Skip to main content
Glama

Get an MCP audit report

get_mcp_test
Read-onlyIdempotent

Get the report of an audit started with test_mcp_server: status (queued, running, done), score, grade, each check with how-to-fix advice, latency and a Markdown version to share.

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": {
      "id": "<id>"
    },
    "name": "get_mcp_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAudit id returned by test_mcp_server.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Id returned when the job was created"New value: +"Audit id returned by test_mcp_server."
  2. Added

TDQS

A3.9/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 closed-world scope, so the safety profile is fully covered by structured data. The description's added value is the payload shape (score, grade, per-check fix advice, Markdown rendering) that would otherwise be invisible with no output schema, but it says nothing about error behavior for an unknown id or whether partially-run audits return partial data.

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?

One sentence, front-loaded with the action and resource, then a compact inventory of the report contents. It is dense but earns its words; the only minor cost is the clustered enumeration of report fields, which reads slightly like a list dump.

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?

With no output schema, the description usefully compensates by previewing exactly what a caller receives, including the Markdown variant for sharing. What is missing is lifecycle guidance — whether the caller should re-call while status is queued/running and whether the report is retained or expires — for an audit tool whose results arrive asynchronously.

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 coverage is 100% and the single id parameter, including its 24-hex pattern and origin, is already documented in the schema. The description's mention that the id comes from test_mcp_server restates the schema's own note rather than adding format, lifetime, or reuse semantics, 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 uses a specific verb ("Get") and resource ("the report of an audit") and anchors it to the sibling that creates it ("started with test_mcp_server"), so an agent can tell this is a retrieval step that follows an audit run. It also enumerates the payload (status, score, grade, checks with fix advice, latency, Markdown), making the tool distinguishable from status-polling siblings like get_request_status.

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?

It clearly establishes the prerequisite context: this is only meaningful for an audit previously started via test_mcp_server, which is the key routing signal an agent needs. It stops short of explicit when-not guidance or advice about polling while status is still "queued"/"running", so the alternative-selection story is implied rather than spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.