Skip to main content
Glama
dotnet-mcp-server-blueprint

dotnet-mcp-server-blueprint

Validate Official MCP Registry Manifest

validate_server_manifest
Read-onlyIdempotent

Validate a server.json payload against Official MCP Registry constraints to catch manifest errors before submission.

Instructions

Validates a server.json payload against Official MCP Registry constraints.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "serverJson": "<serverJson>"
    },
    "name": "validate_server_manifest"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverJsonYesRaw JSON content of server.json.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds only the target standard ('Official MCP Registry constraints'); it does not say whether failures return a list of violations, throw, or what happens with malformed JSON.

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?

One front-loaded sentence with no filler; the action and the target are stated immediately.

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

Completeness3/5

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

For a read-only validator with one parameter and no output schema, the definition should hint at what the validation returns (pass/fail, error list) since no structured return contract exists. The essentials for calling it are present, but the result shape is left unclear.

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?

With a single parameter at 100% schema description coverage, the schema already explains serverJson as raw JSON content. The description adds no format details (e.g., whether a file path or stringified object is accepted), so baseline 3 applies.

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

Purpose4/5

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

States a specific verb (validates) and resource (server.json payload) plus the standard it validates against (Official MCP Registry constraints). An agent can tell this is a schema/constraint checker rather than a policy summarizer or trust evaluator, though it doesn't explicitly name the siblings.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no mention of the alternatives (evaluate_mcp_trust_boundary, generate_tool_policy_summary). The agent must infer that this precedes publishing a manifest to the registry.

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