Server Quality Checklist

Tool Scores

• get_monitor_badgeA
  4.2/5.0
  Behavior4/5

  Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

  Annotations already declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds complementary behavioral context: the tool emits embeddable snippets and links reflecting real-time monitor status rather than mutating anything. No contradiction with annotations; the generate-and-return behavior is fully consistent with a read-only hint.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  Two sentences, front-loaded with the core function, followed by concrete usage context. No filler words; each sentence earns its place.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  The tool is simple (one parameter, no nested objects), has a full input schema, a read-only annotation, and an output schema. The description covers purpose, output artifact type, displayed content, and target destinations. Nothing essential for an agent to invoke it correctly is missing; the output schema handles return-value details.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 100%, with the monitorId parameter fully documented including examples ('demo', 'mon_prod_01', 'sample') and an explanation of preview values. The tool description adds no parameter-level details beyond the schema, so the baseline of 3 is appropriate.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description names a specific verb ('Generates'), a concrete artifact ('dynamic SVG status badge links and Markdown embed snippets'), and a clear domain ('MCP Sentinel uptime monitor'). The contents of the badge (real-time operational status, protocol version, uptime) are explicit. The sibling tools (audit_mcp_server, verify_mcp_protocol) perform clearly different actions, so no confusion is possible.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The second sentence gives an explicit trigger condition: 'Use this tool when you want to display...' with concrete destinations (GitHub README, developer documentation, status page). It does not name alternatives or state when not to use the tool, but the usage context is specific enough for an agent to route correctly.

  Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

• verify_mcp_protocolA
  4.2/5.0
  Behavior4/5

  Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

  Annotations already provide readOnlyHint=true and openWorldHint=true, and the description adds meaningful behavioral context: version negotiation targets, handshake latency benchmarking, capability/tool count inspection, and no vulnerability scanning. This goes beyond the annotations without contradicting them.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  Two sentences with no filler. The core action is front-loaded, and every clause adds useful context: supported protocol versions, latency benchmarking, capability inspection, and the exclusion of vulnerability scanning.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  The description covers purpose, use cases, and exclusions, while the schema documents both parameters and an output schema exists. It could be slightly stronger by explicitly directing users to audit_mcp_server for full vulnerability scans, but nothing critical is missing for a read-only protocol check.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 100%, and both endpointUrl and authHeader have clear descriptions and examples. The description itself does not add parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  Description opens with a specific verb and resource: 'Validates JSON-RPC 2.0 protocol compatibility and version negotiation with a remote MCP server'. It also distinguishes itself from the sibling audit_mcp_server by explicitly stating it is 'without executing a full synthetic vulnerability scan'.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  Gives an explicit use-this-when list: 'Use this tool when you specifically need to test whether a remote server supports...' and covers several concrete scenarios. It also states what the tool is not ('without executing a full synthetic vulnerability scan'), but it does not explicitly name the alternative tool, audit_mcp_server, so the guidance is clear but not fully complete.

  Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

• audit_mcp_serverA
  4.3/5.0
  Behavior4/5

  Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

  Annotations already declare readOnlyHint and openWorldHint, so the description only needs to add contextual behavior. It adds that the audit is 'synthetic', enumerates the checks performed, and discloses the return format (markdown diagnostic report and structured status flags). This is useful, non-redundant behavioral context with no annotation contradiction.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is three dense sentences: purpose, trigger conditions, and output. It is front-loaded with the core action, avoids filler, and does not restate the input schema. Every sentence earns its place.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness5/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  With only two fully documented parameters, an output schema, and readOnly annotations, the description covers the tool's scope, when to use it, and what it returns. An agent has enough information to select and invoke the tool correctly without missing critical context.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 100%, and both parameters already have clear descriptions, formats, and examples. The tool description adds no parameter-specific semantics beyond what the schema provides, so the baseline score of 3 is appropriate.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description opens with a specific verb ('Performs') and precise resource ('audit on any remote MCP server'), then enumerates the audit dimensions: health, protocol compliance, schema validation, and credential security. Although sibling tools are not named, the comprehensive-audit framing clearly distinguishes this tool from verify_mcp_protocol and get_monitor_badge.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description includes an explicit 'Use this tool when you need to...' clause listing concrete use cases such as checking reachability, latency, schema compliance, broken parameters, and exposed credentials. It lacks when-not-to-use guidance or explicit alternative routing, so it does not reach a 5.

  Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.