Skip to main content
Glama
Sign In
@mhdd_24/api-versioning-mcp

@mhdd_24/api-versioning-mcp

by Mhdd-24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

apiver_strategy

Suggests API versioning strategy notes for URL, header, or query styles to help resolve version compatibility decisions.

Instructions

Suggest versioning strategy notes.

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

Input Schema

NameRequiredDescriptionDefault
styleNourl|header|query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about whether the tool reads only or mutates state, what the returned 'notes' contain, or any auth/rate constraints. 'Suggest' implies advisory output but is left ambiguous.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no wasted words, but its brevity comes at the cost of substance rather than being tightly front-loaded information. Adequate structure, minimal content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description must explain the return artifact, and it does not. For a tool whose whole value is the 'notes' it produces, the key output is undefined.

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?

Schema description coverage is 100% (the style param documents 'url|header|query'), so the schema already carries the field meaning. The description adds nothing about how style affects the suggested strategy, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ('Suggest') and a resource ('versioning strategy notes'), so it is not mere tautology, but 'notes' is vague and it never distinguishes itself from siblings apiver_status and apiver_compare. An agent cannot tell what artifact is produced or how this differs from comparing or checking version status.

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 when-to-use guidance, no prerequisites, and no mention of the sibling tools as alternatives. The agent must infer that this tool produces advisory output rather than status or comparison data.

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