OpenAPI MCP Gateway

Updates a pet in the store with form data.

update_pet_with_form

Update a pet's name and status using form data. Provide the pet ID and new values to modify an existing pet record.

Instructions

Updates a pet resource based on the form data.

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

Input Schema

Name	Required	Description
`name`	No	Name of pet that needs to be updated
`petId`	Yes	ID of pet that needs to be updated
`status`	No	Status of pet that needs to be updated

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.6.2Aug 11, 2026
- removedInput schema / properties / name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / name / default
```
Removed value: -null
```
- removedInput schema / properties / name / title
```
Removed value: -"Name"
```
- addedInput schema / properties / name / type
```
Added value: +"string"
```
- addedInput schema / properties / petId / format
```
Added value: +"int64"
```
- removedInput schema / properties / petId / title
```
Removed value: -"Petid"
```
- removedInput schema / properties / status / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / status / default
```
Removed value: -null
```
- removedInput schema / properties / status / title
```
Removed value: -"Status"
```
- addedInput schema / properties / status / type
```
Added value: +"string"
```
- removedInput schema / title
```
Removed value: -"upstream_callableArguments"
```
First observedv1.0.0Jun 11, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations provide no readOnly or destructive hints, so the description must disclose safety and behavioral traits. It only restates that it updates a pet, with no information about authentication, idempotency, partial updates, or response behavior. This is insufficient for a mutation tool.

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?

The description is short and non-redundant internally, but it largely duplicates the title 'Updates a pet in the store with form data.' It does not add new information, so while concise, it doesn't earn its place as a value-adding description.

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?

The tool is simple and schema covers parameters, but the description is minimal. It omits the form-encoding distinction from 'update_pet' and any response expectations. Given the absence of an output schema, a brief note on usage context would improve completeness.

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?

All three parameters have clear schema descriptions ('Name of pet that needs to be updated', etc.), so the description does not need to add param-level detail. The phrase 'based on the form data' vaguely connects to the parameters but adds no concrete semantics. Schema coverage is 100%, so baseline 3 applies.

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 specifies the action ('updates') and resource ('pet'), making the core function clear. However, it fails to distinguish from the sibling tool 'update_pet', which likely updates a pet via JSON rather than form data, so the specificity is incomplete.

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?

The description provides no guidance on when to use this tool instead of alternatives. It does not mention the 'form' aspect as a deciding factor, nor does it reference 'update_pet' for JSON payloads. Agents must infer usage from the tool name.

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