inavi-mcp

Official

Overview Schema Source Related Servers Discussions Admin

Get INAVI Maps API Specification

get_api_spec

Retrieve a specific iNavi Maps API's full specification by operationId—including parameters, request body, and response schemas—after browsing available APIs with 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

Name	Required	Description	Default
`operationId`	Yes	Unique identifier of the API to retrieve (e.g., getRouteTimeResult)

Output Schema

Name	Required	Description
`path`	Yes	API path
`tags`	Yes	API category tags
`method`	Yes	HTTP method
`baseUrl`	Yes	Base URL
`summary`	Yes	Brief API description
`category`	Yes	API category (route, search)
`responses`	Yes	Response schemas by status code
`deprecated`	No	Whether the API is deprecated
`parameters`	No	List of API parameters
`description`	Yes	Detailed API description
`operationId`	Yes	Unique API identifier
`requestBody`	No	Request body schema

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.4.1Sep 23, 2026
- addedOutput schema / properties / parameters / items / additionalProperties
```
Added value: +true
```
- addedOutput schema / properties / parameters / items / properties
```
Added value: +{}
```
- addedOutput schema / properties / parameters / items / type
```
Added value: +"object"
```
- addedOutput schema / properties / requestBody / additionalProperties
```
Added value: +true
```
- addedOutput schema / properties / requestBody / properties
```
Added value: +{}
```
- addedOutput schema / properties / requestBody / type
```
Added value: +"object"
```
- addedOutput schema / properties / responses / additionalProperties / additionalProperties
```
Added value: +true
```
- addedOutput schema / properties / responses / additionalProperties / properties
```
Added value: +{}
```
- addedOutput schema / properties / responses / additionalProperties / type
```
Added value: +"object"
```

Changed2 schema fields changedv0.3.10Jul 24, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

First observedv0.3.9Jul 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the burden and clearly implies a read-only retrieval. It usefully discloses that all $ref references have already been dereferenced and that the full specification includes parameters, request body, and response schemas, though it does not discuss error behavior or permissions.

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 front-loaded and structured with PREREQUISITE, USAGE, and NOTE sections. Every sentence adds actionable information without repetition.

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?

Given a single required parameter, full schema coverage, and an output schema, the description is complete enough for correct invocation. It covers the prerequisite, the input semantics, and the important dereferencing detail.

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 coverage is 100%, so the operationId parameter is already fully documented with an example. The description reinforces that operationId identifies the API but does not add format or syntax details beyond the schema.

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 states a specific verb and resource: retrieves the detailed specification of a specific API, including request/response schemas. It clearly distinguishes itself from the sibling list_api_specs by focusing on one API identified by operationId.

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?

It gives an explicit prerequisite to first use list_api_specs to browse APIs and obtain the operationId, and then states the usage pattern for retrieval. The alternative workflow is named directly, leaving little inference required.

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

Deploy Server