Skip to main content
Glama
Sign In
MCP QA Lab

MCP QA Lab

by efficjump
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

run_static_checks

Read-only

Run static checks to analyze a target's schemas, descriptions, annotations, and size without tool calls, identifying usability and context-cost issues early.

Instructions

Analyze live schemas, descriptions, annotations, and size without tool calls.

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": {
      "target_id": "<target_id>"
    },
    "name": "run_static_checks"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_idYesIdentifier returned by register_target.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only and non-destructive behavior. The description adds the key behavioral guarantee 'without tool calls', clarifying that no target tool is executed, and 'live' indicates it reads current state. This adds useful context beyond 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?

A single sentence, front-loaded with the action verb, and contains no filler, redundancy, or extraneous information.

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 one fully-documented parameter, an output schema, and safety annotations, the description covers the essential behavior of static analysis. It is sufficient for the tool's low complexity, though it could mention the relationship to sibling tools like inspect_target for greater completeness.

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?

The input schema fully documents the single parameter target_id, and schema description coverage is 100%. The description adds no extra parameter semantics, so the baseline score of 3 applies.

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 the specific verb 'Analyze' and names concrete resources: 'live schemas, descriptions, annotations, and size'. The clause 'without tool calls' distinguishes it from siblings like run_target_tool, clearly positioning it as a static inspection tool.

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 phrase 'without tool calls' provides clear context for using this tool when non-invasive inspection is needed, implicitly contrasting with execution tools. However, it does not explicitly name alternatives or when-not-to-use conditions, so it stops short of a 5.

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

Deploy Server

Other Tools