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

dotnet-mcp-server-blueprint

Generate Tool Policy Summary

generate_tool_policy_summary
Read-onlyIdempotent

Classifies an MCP tool into a least-privilege capability scope and approval policy from its read-only, destructive, and external-network attributes.

Instructions

Classifies an MCP tool into a least-privilege capability scope and approval policy.

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": {
      "toolName": "<toolName>",
      "isReadOnly": "<isReadOnly>",
      "isDestructive": "<isDestructive>",
      "touchesExternalNetwork": "<touchesExternalNetwork>"
    },
    "name": "generate_tool_policy_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNameYesCanonical snake_case tool name.
isReadOnlyYesTrue if the tool only reads state.
isDestructiveYesTrue if the tool performs destructive or irreversible actions.
touchesExternalNetworkYesTrue if the tool accesses external third-party URLs or APIs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description's burden is lighter. The description adds that the result is a scope/approval-policy classification (pure computation), but says nothing about whether the classification is deterministic, how it is derived from the boolean inputs, or what the result looks like.

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 efficient sentence with no filler and the purpose front-loaded. It is arguably undersized rather than oversized, so no credit lost for verbosity.

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?

With no output schema, the description carries the burden of explaining the return value, and it only gestures at it ('capability scope and approval policy') without stating the shape, allowed values, or whether an approval tier is returned. For a tool whose entire value is its classification output, that is a real gap, though the inputs and intent are otherwise clear.

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 all four required parameters documented (toolName, isReadOnly, isDestructive, touchesExternalNetwork), so the schema does the heavy lifting and baseline 3 applies. The description adds no meaning about how these flags feed into the classification.

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 ('Classifies') and resource ('an MCP tool') plus the two classification targets (least-privilege capability scope and approval policy). An agent can tell this apart from validate_server_manifest or evaluate_mcp_trust_boundary by the output it produces, though no sibling is named.

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 when-to-use guidance, no stated prerequisites, and no reference to alternatives. The description never says whether this should be called before or after validate_server_manifest, or under what circumstances an agent should invoke it at all.

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