Skip to main content
Glama

findPetsByTags

Read-onlyIdempotent

Filter pets by one or more tags to retrieve animals that match specific categories or labels.

Instructions

Finds Pets by tags.

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": {
      "tags": "<tags>"
    },
    "name": "findPetsByTags"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsYesTags to filter by

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds nothing beyond them: it does not say how multiple tags combine (AND vs OR), whether matching is case-sensitive, or what happens when no pet matches. For a filter endpoint that ambiguity matters.

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

Conciseness3/5

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

One short sentence with zero padding, so it is trivially front-loaded and free of waste. Brevity here is under-specification rather than efficiency, since the sentence carries almost no information.

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?

This is a low-complexity tool with rich annotations and a fully described schema, so little is required. Still, the key open question for a tag filter — whether multiple tags narrow or widen results — is answered nowhere in description, schema, or output schema.

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?

The single parameter is fully documented in the schema ("Tags to filter by"), so the schema carries the weight and baseline 3 applies. The description does not add syntax, array-length limits, or combination semantics beyond that.

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

Purpose2/5

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

"Finds Pets by tags" only expands the camel-case name into a sentence; it names no behavior the tool name does not already imply. It does gesture at the resource and filter, but there is no distinguishing detail versus a sibling like findPetsByStatus beyond the word "tags".

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 choose this over findPetsByStatus or getPetById, and no note on preconditions such as needing an existing tag or an authenticated session. The agent must infer the selection rule from the tool names alone.

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