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

dotnet-mcp-server-blueprint

Evaluate MCP Trust Boundary

evaluate_mcp_trust_boundary
Read-onlyIdempotent

Evaluate an MCP server deployment against trust-boundary best practices to flag risks in transport, authentication, input validation, read-only behavior, and shell command execution.

Instructions

Evaluates an MCP server deployment configuration against trust-boundary best practices.

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": {
      "transport": "<transport>",
      "isReadOnly": "<isReadOnly>",
      "validatesInputs": "<validatesInputs>",
      "executesShellCommands": "<executesShellCommands>",
      "requiresAuthentication": "<requiresAuthentication>"
    },
    "name": "evaluate_mcp_trust_boundary"
  }
}

Input Schema

NameRequiredDescriptionDefault
transportYesTransport type: 'stdio', 'http', or 'streamable-http'.
isReadOnlyYesTrue when every tool avoids external state mutations.
bindAddressNoOptional listen address when using HTTP transport (e.g. 127.0.0.1).
validatesInputsYesTrue when all tool arguments are schema-validated and canonicalized.
executesShellCommandsYesTrue when any tool can invoke arbitrary OS shell commands.
requiresAuthenticationYesTrue when HTTP/network transport requires caller authentication.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/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 the safety profile is covered. The description adds that the evaluation is against 'trust-boundary best practices,' which scopes the criteria, but says nothing about what checks are performed, whether sub-scores or a verdict are produced, or how failure is signaled.

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

Conciseness4/5

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

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity edges toward under-specification rather than crispness.

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

Completeness2/5

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

There is no output schema and the description never indicates what the evaluation returns—a pass/fail verdict, a list of findings, severity levels, or remediation advice. For a 6-parameter diagnostic tool, the omission of result shape and evaluation criteria is a substantive gap.

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% for all 6 parameters, including transport enum values and the meaning of each boolean, so the schema carries the semantics. The description contributes nothing additional about how the parameters interact (e.g., that bindAddress only matters for HTTP transport beyond what the schema notes).

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?

The description names a specific verb ('Evaluates'), a specific resource ('an MCP server deployment configuration'), and the evaluation basis ('trust-boundary best practices'). It is clearly a read-only diagnostic, but it does not distinguish itself from siblings like validate_server_manifest or generate_tool_policy_summary, which sound like adjacent configuration-analysis tools.

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 statement of when to use this tool versus validate_server_manifest or generate_tool_policy_summary, nor any prerequisite or exclusion. The agent must infer from the name alone that this is the trust/security-oriented check rather than schema validation.

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