Skip to main content
Glama
mcp-feature-test

mcp-feature-test

by linuxrrze

Structured output with an array root

structured_output_array
Read-only

Returns metrics whose outputSchema has an array root and unwraps the {"result": [...]} envelope used by 2025-era connections.

Instructions

Return a list of metrics whose outputSchema has an array root. Allowed on 2026-07-28 (SEP-2106); on 2025-era connections the schema and the value arrive wrapped as {"result": [...]}.

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_array"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYesName/value pairs (array root)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real value beyond that by disclosing a version-dependent behavioral difference: on 2026-07-28 (SEP-2106) the array is the root, while on 2025-era connections both schema and value arrive wrapped as {"result": [...]} — exactly the kind of context an agent cannot get from annotations or schema.

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?

Two dense sentences with zero filler. The core purpose is front-loaded and the conditional protocol caveat follows it, so an agent can stop reading after the first clause if the fallback behavior is irrelevant.

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 return shape need not be spelled out, and the description still covers the one thing the schema cannot: how the value is wrapped depending on connection era. It stops just short of explaining what the metrics themselves represent.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4; nothing about argument meaning needs explaining and the description correctly spends no words on inputs.

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 uses a specific verb-plus-resource ('Return a list of metrics') and scopes it to outputs whose outputSchema has an array root, which is far more informative than the title alone. It doesn't distinguish itself from the sibling 'structured_output', 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?

Usage is only implied: the tool is a probe that produces an array-rooted structured result. There is no explicit statement of when to call it versus the sibling 'structured_output', and no when-not guidance; the protocol-date sentence describes behavior, not selection criteria.

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