Skip to main content
Glama
Sign In
mcp-swagger

mcp-swagger

by awssam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

getEndpointsByTag

Retrieve all endpoints associated with a specified tag to find relevant API operations in Swagger documentation.

Instructions

Récupère tous les endpoints associés à un tag spécifique. Plus ciblé que listEndpoints avec filtre.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tag": "<tag>"
    },
    "name": "getEndpointsByTag"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYesLe tag pour lequel récupérer les endpoints

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It clearly indicates a read operation ('Récupère') and provides the filtering scope, but does not disclose potential pagination, ordering, or what constitutes an 'endpoint' in the response. It is minimally transparent but not misleading.

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?

The description is a single, focused sentence that immediately states the tool's purpose and relevance. No wasted words; every word earns its place.

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

Completeness3/5

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

With no output schema, the description does not explain the return format, but the tool is simple (one parameter, read-only intent). It does not mention pagination or result details, but for a basic retrieval oriented around tags, the description is minimally sufficient. A more complete description could note whether endpoint summaries or full details are returned.

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 input schema fully describes the only parameter 'tag' with a description, achieving 100% coverage. The description adds little beyond the schema, merely echoing 'tag spécifique'. Baseline 3 is appropriate as the schema carries the parameter meaning.

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

Purpose5/5

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

The description clearly states the verb 'Récupère' (retrieves) and the resource 'endpoints' scoped by a 'tag spécifique'. It explicitly distinguishes itself from listEndpoints by noting it is 'Plus ciblé' (more targeted), which sets it apart from a sibling.

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

Usage Guidelines5/5

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

The description provides direct when-to-use guidance by comparing with listEndpoints and indicating this tool is more targeted when a specific tag is involved. It names the alternative tool, fulfilling the requirement for explicit alternatives.

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