Skip to main content
Glama
Sign In
OpenAPI MCP Gateway

OpenAPI MCP Gateway

by mroops0111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Returns pet inventories by status.

get_inventory
Read-onlyIdempotent

Returns a map of status codes to quantities for quick assessment of inventory stock levels.

Instructions

Returns a map of status codes to quantities.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.2
    • removedInput schema / title
      Removed value: -"upstream_callableArguments"
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, covering the safety profile. The description adds the return type (map of status codes to quantities) but does not disclose any additional behavioral traits such as auth requirements, rate limits, or side effects beyond what annotations provide.

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 sentence, eight words long, with no redundant text. It is front-loaded with the verb and resource, and every word earns its place.

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

Completeness4/5

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

For a simple no-parameter, read-only tool, the description is adequate. It specifies the return shape (map of status codes to quantities), which is critical since there is no output schema. It does not enumerate possible status codes, but this is inferable and not necessary for operation.

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?

The tool has zero parameters, and the schema description coverage is 100% (empty schema). With no parameters, the description does not need to add parameter semantics. Baseline for 0 params is 4, and the description does not introduce confusion.

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 tool 'Returns a map of status codes to quantities', which is a specific verb (returns) and resource (inventory map). This distinguishes it from sibling tools like get_pet_by_id or find_pets_by_status, which focus on pets rather than inventory.

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?

No usage guidance is provided. The description does not state when to use this tool versus alternatives, nor does it mention any context such as 'use for stock levels' or 'prefer over find_pets_by_status for inventory counts'.

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