PestPin

Pest control cost range

get_pest_cost

Read-onlyIdempotent

US national planning cost range for a pest control service, with the factors that move the price. This is an editorial planning range, not a quote and not a measured average; the actual price for a job comes from a written local quote.

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": {
      "pest": "<pest>"
    },
    "name": "get_pest_cost"
  }
}

Input Schema

Name	Required	Description	Default
`pest`	Yes	Pest or service, e.g. termite control, bed bugs

Output Schema

Name	Required	Description
`note`	Yes
`pest`	Yes
`answer`	No	Short direct answer a person can read out
`details`	No	PestPin cost page for this pest
`priceFactors`	No
`nationalPlanningRangeUsd`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 8, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / pest / examples

Added value: +[
+  "termite control",
+  "bed bugs"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "answer": {
+      "description": "Short direct answer a person can read out",
+      "type": "string"
+    },
+    "details": {
+      "description": "PestPin cost page for this pest",
+      "type": "string"
+    },
+    "nationalPlanningRangeUsd": {
+      "properties": {
+        "high": {
+          "type": "integer"
+        },
+        "low": {
+          "type": "integer"
+        },
+        "typical": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "low",
+        "high",
+        "typical"
+      ],
+      "type": "object"
+    },
+    "note": {
+      "type": "string"
+    },
+    "pest": {
+      "type": "string"
+    },
+    "priceFactors": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "pest",
+    "nationalPlanningRangeUsd",
+    "note"
+  ],
+  "type": "object"
+}

First observedAug 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds important behavioral context: it is an editorial range, not a measured average, and includes factors that move price. This goes beyond what annotations state, clarifying scope and limitations.

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

Conciseness5/5

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

The description is two sentences, front-loaded with the core purpose and then immediately clarifying limitations. No wasted words; every phrase adds value.

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

Completeness5/5

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

The description fully explains the nature of the return (a planning range, not a quote) and its intended use. Given the output schema presumably describes result structure, nothing else is needed. The tool's purpose, limitations, and context are clearly conveyed.

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?

Schema description coverage is 100%, so the 'pest' parameter is fully described in the schema with examples. The description doesn't add specific parameter details, but its mention of 'factors that move the price' hints at how the parameter influences the result. This is adequate given the schema coverage.

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

Purpose5/5

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

The description clearly states the tool provides a 'US national planning cost range for a pest control service' with factors that move the price. It immediately distinguishes itself from siblings like get_price_card (which likely gives specific quotes) by clarifying this is an editorial range, not a quote.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly contrasts the planning range with a 'written local quote', implying it should be used for rough estimates rather than actual pricing. It notes it is not a quote or measured average, giving strong context for when to use it. However, it doesn't explicitly name alternative tools that should be used in its place.

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

All PestPin tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?