Skip to main content
Glama
mcp-feature-test

mcp-feature-test

by linuxrrze

Inspect client capabilities

inspect_client
Read-only

Report the protocol version, client info, and declared capabilities to verify which frontend features the current client supports.

Instructions

Report the protocol version, client info and declared client capabilities (elicitation form/url, MCP Apps UI extension, sampling, roots). Use it to check what the current frontend supports.

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": "inspect_client"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, so the safety profile is covered. Beyond that, the description discloses the payload's content by naming the capability groups returned, which is genuinely useful since there is no output schema. It says nothing about failure modes or whether capability absence is reported as false versus omitted, which is a minor residual gap.

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 sentences, no filler. The content of the report is front-loaded and the usage condition follows, so an agent can stop reading after sentence one if it only needs to know what the tool returns.

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 zero parameters and no output schema, the description carries the burden of describing the return value, and it does so by listing the capability categories. That is sufficient to decide whether to call it. It could be marginally stronger by noting that capabilities reflect only what the client declared at initialization.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies a no-argument call by framing the tool as reporting on 'the current frontend' rather than accepting a target.

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 opens with a specific verb ('Report') and enumerates exactly what is reported: protocol version, client info, and declared capabilities (elicitation form/url, MCP Apps UI extension, sampling, roots). That is far more concrete than a name-only restatement. It stops short of naming a sibling such as list_roots or list_seen_clients to disambiguate, so it is clear but not sibling-differentiated.

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 gives an explicit use condition: 'Use it to check what the current frontend supports.' That is a clear trigger for invoking the tool. It offers no exclusions or alternative-routing guidance (e.g., when to prefer list_roots for roots specifically), which keeps it out of the 5 tier.

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