DeepWiki

v2.14.3 · 3 tools · source

[ tools: 3 ][ checks: 13 ][ latency: 579ms ]

81/100(C)

remote: https://mcp.deepwiki.com/mcp

check breakdown

✓Tools exposed — Server exposed 3 tools.

• ask_question

• read_wiki_contents

• read_wiki_structure

✓Input schemas valid — All tools have a valid JSON-Schema input definition.

!Input schema quality — 3 schema-quality issue(s) across 3 tool(s).

ask_question: inputSchema.additionalProperties is not set to false (extra args pass through silently)

read_wiki_contents: inputSchema.additionalProperties is not set to false (extra args pass through silently)

read_wiki_structure: inputSchema.additionalProperties is not set to false (extra args pass through silently)

→ Declare `required` for every schema that has properties, so agents know which params are mandatory.

→ Give every property a `description` and a concrete `type` (avoid bare `{}` placeholders).

→ Set `additionalProperties: false` on the top-level inputSchema so models can't silently pass extra, unvalidated arguments.

✓Output schemas — All tools declare a valid outputSchema.

✓Duplicate tool names — All tool names are unique.

✓Tool naming — All tool names use spec-legal characters.

✓Descriptions — Every tool and parameter is clearly described.

!Tool annotations — Annotation coverage 0% (0/15 hint fields set).

• ask_question: no annotations at all

• read_wiki_contents: no annotations at all

• read_wiki_structure: no annotations at all

→ Add annotations: title, readOnlyHint, destructiveHint, idempotentHint, openWorldHint.

→ These let clients gate risky calls and give agents/users a friendly display name — optional but valuable.

!Tool titles — 3 of 3 tool(s) have no title.

• ask_question: no top-level title (or annotations.title)

• read_wiki_contents: no top-level title (or annotations.title)

• read_wiki_structure: no top-level title (or annotations.title)

→ Declare a top-level `title` on each tool — it gives clients a friendly display name distinct from the machine-readable `name`.

→ `annotations.title` (the older location) is also accepted, but the top-level `title` field is now the spec-preferred place for it.

✓Server instructions — Server declares top-level instructions for clients.

✓Handshake + list latency — tools/list responded in 579ms.

!Prompts — Server declares the prompts capability but exposes 0 prompts.

→ If you don't actually offer prompts, remove the `prompts` capability from your initialize response.

→ Otherwise, register at least one prompt via your prompts/list handler.

!Resources — Server declares the resources capability but exposes 0 resources.

→ If you don't actually offer resources, remove the `resources` capability from your initialize response.

→ Otherwise, register at least one resource (or resource template) via your resources/list handler.

Paste into your README:

[![scoremcp](https://scoremcp.dev/badge/deepwiki)](https://scoremcp.dev/servers/deepwiki)