Skip to main content
Glama
Sign In
Universal MCP Bridge & Proxy

Universal MCP Bridge & Proxy

by francaroscillidev-gif
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

getPetById

Retrieves pet details by ID so you can look up a specific pet in the connected API or database.

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

Input Schema

NameRequiredDescriptionDefault
kwargsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing beyond the name. It does not state whether the call is read-only, what happens on a missing or invalid ID, or whether the result is a single record or an empty response.

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?

The definition is a single short, front-loaded phrase with no wasted wording. Its brevity is efficient, though it borders on under-specification rather than deliberate concision.

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?

With no annotations, no output schema, no enums, and an undocumented required parameter, the description is far too thin for an agent to invoke this reliably. It should at minimum explain the parameter and the not-found behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter is an opaque string named 'kwargs' with 0% schema coverage, and the description never explains that the pet ID belongs there or what format it takes. Saying 'by ID' hints at the value but leaves the wrapper and encoding undocumented in both schema and text.

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?

The description states a specific verb and resource ('Find pet by ID'), making the retrieval intent immediately clear. It does not distinguish itself from the closest sibling findPetsByStatus or explain how this differs from a status-based listing, so it stops short of a 5.

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 use this versus findPetsByStatus, no mention of prerequisites such as a valid ID, and no statement about behavior when no pet matches. The agent must infer all routing decisions from the tool name alone.

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