Skip to main content
Glama

Petstore MCP Server

by ai.com.mcp
OverviewDiscussionsAdmin

placeOrder

Place an order for a pet. - Place a new order in the store.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
placeOrderBodyNo
x-hapi-auth-stateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / body
      Removed value: -{
-  "properties": {
-    "complete": {
-      "type": "boolean"
-    },
-    "id": {
-      "format": "int64",
-      "type": "integer"
-    },
-    "petId": {
-      "format": "int64",
-      "type": "integer"
-    },
-    "quantity": {
-      "format": "int32",
-      "type": "integer"
-    },
-    "shipDate": {
-      "format": "date-time",
-      "type": "string"
-    },
-    "status": {
-      "description": "Order Status",
-      "enum": [
-        "placed",
-        "approved",
-        "delivered"
-      ],
-      "type": "string"
-    }
-  },
-  "type": "object"
-}
    • addedInput schema / properties / placeOrderBody
      Added value: +{
+  "properties": {
+    "complete": {
+      "type": "boolean"
+    },
+    "id": {
+      "format": "int64",
+      "type": "integer"
+    },
+    "petId": {
+      "format": "int64",
+      "type": "integer"
+    },
+    "quantity": {
+      "format": "int32",
+      "type": "integer"
+    },
+    "shipDate": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "status": {
+      "description": "Order Status",
+      "enum": [
+        "placed",
+        "approved",
+        "delivered"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • removedInput schema / required
      Removed value: -[
-  "body"
-]
  2. First observed

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It implies a write operation (placing an order) but does not mention side effects, required authentication (despite the x-hapi-auth-state parameter), or any consequences. The description is too minimal to satisfy the transparency burden.

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 but redundant, with two clauses saying essentially the same thing. It could be reduced to a single phrase like 'Create a new order for a pet in the store.' The redundancy wastes a sentence without adding information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (nested object, auth state, many related siblings), the description is severely under-specified. It doesn't explain what an order is, what parameters are needed, what the response will be, or any operational context. For a creation tool with this schema, far more detail is required.

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

Parameters1/5

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

The schema has 0% description coverage and the tool description does not mention any parameters. It never explains that an order requires petId, quantity, status, etc., leaving the agent without semantic understanding of the input fields.

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 clearly states it places/creates a new order for a pet, which distinguishes it from siblings like deleteOrder, getOrderById, and updatePet. However, the phrasing is slightly redundant ('Place an order' + 'Place a new order'), but it still clearly identifies the action and resource.

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 versus alternatives such as addPet, updatePet, or deleteOrder. It doesn't mention any prerequisites, context, or exclusions, so usage context is entirely absent.

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

All Petstore MCP Server toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources