Skip to main content
Glama

getPetById

Read-onlyIdempotent

Fetches a pet record by its numeric ID, enabling you to retrieve pet details from an API through the pluit MCP server.

Instructions

Find pet by ID.

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": {
      "petId": "<petId>"
    },
    "name": "getPetById"
  }
}

Input Schema

NameRequiredDescriptionDefault
petIdYesID of pet to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no note on not-found behavior, no indication of whether the response is a single object, and no caching or rate considerations.

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 key qualifier (by ID) front-loaded and no wasted wording. It is terse but not padded, though the same length could have carried one routing hint.

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?

For a simple single-key lookup with full schema coverage, rich annotations and no output schema, the definition is minimally sufficient. It leaves out not-found semantics and authentication requirements, which matter for an openWorldHint tool hitting an external service.

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?

There is only one parameter and the schema documents it at 100% coverage ("ID of pet to return"), so the baseline of 3 applies. The description contributes no additional meaning such as ID provenance or valid ranges.

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

Purpose4/5

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

"Find pet by ID" gives a specific verb (find) and resource (pet) plus the lookup key, which is enough to tell it apart from getOrderById or getUserByName by resource. It stops short of explicitly contrasting with findPetsByStatus/findPetsByTags, which fetch collections rather than a single pet.

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 guidance on when to prefer this over the sibling search tools, no statement of prerequisites (e.g. authentication), and no mention of what to do when the ID is unknown. The agent must infer usage entirely from the name.

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