Skip to main content
Glama
mcp-feature-test

mcp-feature-test

by linuxrrze

Structured output (outputSchema)

structured_output
Read-only

Returns a fake build report as schema-declared structured content, with variants for valid data, text mismatches, invalid schema data, and isError results to test client handling.

Instructions

Return a fake build report as structuredContent, declared by an outputSchema. Variants: object (valid data plus the same JSON as text, as the spec recommends), data_only (valid data, no text block at all), text_differs (the text block reports different numbers than the data), invalid (data that violates the outputSchema), error (an isError result without structuredContent, which the spec allows).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "structured_output"
  }
}

Input Schema

NameRequiredDescriptionDefault
variantNoobject

Output Schema

NameRequiredDescriptionDefault
tagsYesFree-form labels
failedYesNumber of failed tests
passedYesNumber of passed tests
statusYesOverall result
projectYesProject name
durationMsYesWall-clock duration in milliseconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, but the description goes far beyond that by disclosing exactly what each variant returns: valid data plus matching text, data with no text block, text that contradicts the data, data that violates the schema, and an isError result without structuredContent. This is precisely the behavioral context an agent needs to predict output shape and interpret intentionally broken responses.

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?

Purpose is front-loaded in the first clause, followed by a compact variant enumeration where each parenthetical earns its place. The variant list is dense but every phrase adds distinct meaning, with no filler.

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 an output schema present, the description need not detail return values, yet it still explains each variant's behavior. It is nearly complete for a spec-probe tool, missing only an explicit note that this is a test/demonstration tool and any differentiation from the array-based sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for the single 'variant' parameter. It defines all five enum values with concrete semantics (e.g. text_differs means the text block reports different numbers than the data), fully compensating for the schema gap.

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 first sentence states a specific action and resource: 'Return a fake build report as structuredContent, declared by an outputSchema.' An agent immediately understands this is an outputSchema demonstration tool. It does not, however, differentiate itself from the sibling structured_output_array, so it falls short of a 5.

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

Usage Guidelines3/5

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

The variants implicitly guide which variant to pick, since each parenthetical describes the resulting behavior. There is no explicit when-to-use framing, no mention of when-not-to-use, and no routing to alternatives such as structured_output_array, so the guidance is implied rather than stated.

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