Skip to main content
Glama
inavi-systems

inavi-mcp

Official
by inavi-systems
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Get iNavi Maps API Specification

get_api_spec

Retrieve a complete API specification with parameters, request body, and response schemas by providing an operationId from list_api_specs.

Instructions

Retrieves detailed specification of a specific API (including request/response schemas). PREREQUISITE: First use list_api_specs to browse available APIs and obtain the operationId. USAGE: Provide an operationId to get the complete API specification including parameters, request body, and response schemas. NOTE: All $ref references have already been dereferenced to actual schema contents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationIdYesUnique identifier of the API to retrieve (e.g., getRouteTimeResult)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAPI path
tagsYesAPI category tags
methodYesHTTP method
baseUrlYesBase URL
summaryYesBrief API description
categoryYesAPI category (route, search)
responsesYesResponse schemas by status code
deprecatedNoWhether the API is deprecated
parametersNoList of API parameters
descriptionYesDetailed API description
operationIdYesUnique API identifier
requestBodyNoRequest body schema

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

No annotations provided, but description discloses that all $ref references are dereferenced, a key behavioral detail. Could mention output format or auth implications, but overall adequate.

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?

Three concise sentences, front-loaded with purpose, no wasted words.

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

Completeness5/5

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

With output schema present, description covers prerequisite, usage, and dereferencing behavior; complete for a simple tool.

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?

Schema covers the single parameter fully; description adds context about obtaining operationId from list_api_specs and gives an example format.

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?

Description clearly states it 'Retrieves detailed specification of a specific API' with specific verb and resource, and distinguishes from sibling tools like list_api_specs.

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?

Explicitly provides prerequisite (first use list_api_specs) and usage instruction, differentiating when to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/inavi-systems/inavi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server