List the three GSC protocols
list_protocolsThe protocol family and the resolve-once spine: ACM-SPARKS classifies, SM-ECO-10060 resolves, ACM-68000 signals.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
MCP CPG Agent Protocols
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.1/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must convey behavior. It fails to state that the tool is a read operation, does not describe side effects, permissions, or return characteristics. The cryptic text adds no behavioral insight.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short but at the expense of clarity. It is cryptic and uses jargon without explanation, making it unhelpful. Conciseness requires effectiveness, not just brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has no output schema, yet the description does not describe what is returned. For a listing tool, the agent needs to know the output format or content. The description is entirely inadequate for an agent to understand the tool's behavior.
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 schema is empty with 100% coverage, meaning no parameters. The description does not add meaning beyond the schema, but absent parameters, a score of 3 is baseline. The description does not explicitly confirm that no input is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
The title states 'List the three GSC protocols', providing a clear verb and resource, but the description is cryptic and does not reinforce or clarify the purpose. It mentions protocol family and specific codes without explaining that the tool lists them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives. Siblings like 'get_protocol' exist but no comparison or context is given. The description does not help an agent decide when to invoke this tool.
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.
TDQS
A3.5/5.0
Disambiguation5/5
Each tool targets a distinct resource (headers, protocols, members, signals, dimensions) with clear actions (get, list, resolve). There is no overlap in functionality; even the two protocol tools differ in granularity (list vs. get).
Naming Consistency4/5
Naming follows a consistent verb_noun pattern using underscores and lowercase. Minor inconsistency: 'list_sparks_dimensions' uses plural while 'resolve_sparks_dimension' uses singular, but overall the pattern is clear.
Tool Count5/5
With 9 tools covering headers, protocols, members, signals, and dimensions, the count is well-proportioned for the domain. Each tool addresses a specific query type without unnecessary bloat or gaps.
Completeness5/5
The tool surface provides complete read access to all canonical entities: headers, protocols, members, signals, and dimensions. Listing and resolving operations are covered for each entity, matching the server's stated purpose of querying agent protocol data.