Skip to main content
Glama

UK dog food brand price history

get_dog_food_price_history
Read-onlyIdempotent

Every dated price BowlPrice has recorded for one UK fresh dog food brand at five dog sizes (3, 7, 14, 30 and 45kg), with each recorded price change and offer change. Brands: butternut-box (Butternut Box), bella-and-duke (Bella & Duke), different-dog (Different Dog), pure-pet-food (Pure Pet Food), tails (tails.com).

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": {
      "brand": "<brand>"
    },
    "name": "get_dog_food_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandYesThe brand's id: butternut-box (Butternut Box), bella-and-duke (Bella & Duke), different-dog (Different Dog), pure-pet-food (Pure Pet Food), tails (tails.com).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With readOnlyHint, idempotentHint and destructiveHint already carrying the safety profile, the description adds real scope information beyond the annotations: the dataset spans five named dog sizes and includes both price changes and offer changes, which tells the agent what granularity of data it gets back. Gaps remain — no mention of how far back history goes or how large a response is — but the additions are substantive.

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 returned-data scope is front-loaded in the first sentence, which is the right ordering, and two sentences is appropriately sized for a single-parameter tool. However, the second sentence repeats the schema's enum list word-for-word, which is dead weight in the description.

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

Completeness4/5

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

For a one-parameter read tool with no output schema and rich annotations, the description supplies the essential missing piece — what the response contains and at what granularity. It would be fully complete with a note on history depth and on how it differs from compare_dog_food_costs, but nothing critical is absent.

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 coverage is 100% and the single brand parameter already enumerates the five ids with human-readable labels; the description's brand list is a verbatim repetition of that. It adds no new meaning such as what happens with an unknown brand or whether a default exists, so the 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 definition names a specific resource — every dated price BowlPrice has recorded for one brand — and specifies coverage (five sizes, price and offer changes). It is clear what the tool returns, but it never mentions the sibling compare_dog_food_costs, so the agent must infer the boundary between 'history for one brand' and 'cost comparison' itself.

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

Usage Guidelines3/5

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

Usage is only implied: the phrase 'every dated price ... with each recorded price change and offer change' signals this is the historical-trend tool, but there is no explicit when-to-use statement, no exclusion, and no pointer to compare_dog_food_costs for the comparison case. An agent could plausibly pick either tool without guidance from this text.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources