Skip to main content
Glama

getInventory

Read-onlyIdempotent

Retrieve pet inventory counts grouped by status to monitor stock levels and availability.

Instructions

Returns pet inventories by status.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered without the description. The description contributes nothing beyond that — it does not say the response is a status-keyed count map, does not mention it is an unfiltered whole-store aggregate, and adds no rate or auth context.

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

Conciseness4/5

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

A single short sentence with the resource front-loaded and no padding. It is efficient, but its brevity is bought by leaving the important ambiguity unresolved.

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?

There is no output schema, so the description carries the full burden of explaining the return value, and it fails to do so — the shape (status to quantity map) is exactly what an agent needs and is not stated. For a no-input aggregate tool, one clause about the return structure would have made it complete.

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?

With zero parameters, the schema imposes no burden and the baseline is a 4. The 'by status' phrasing, however, actively implies a status input that does not exist, which can mislead an agent into looking for a parameter rather than treating this as a no-argument call.

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 verb 'Returns' and resource 'pet inventories' are named, which distinguishes it from getPetById and findPetsByStatus at a glance. However, 'by status' is ambiguous: it reads like a filter even though the tool takes no parameters, so the agent cannot tell whether the results are grouped by status or filtered by one.

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 and no reference to alternatives, even though findPetsByStatus is a plausible overlap for the word 'status'. The agent must infer entirely on its own whether this is an aggregate summary or a listing.

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