Skip to main content
Glama

Local offer

local_offer
Read-onlyIdempotent

Live Local and Maps offers, prices, and the request form URL. Read only. Does not take an order or a payment.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "local_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully structured. The description's added value is the capability boundary (no ordering, no payment), but it says nothing about data freshness, currency, or where the offer data originates, which matters for a 'live' offers feed.

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?

Three short sentences, front-loaded with what is returned and followed by the constraints; nothing is padded. The 'Read only' sentence mildly duplicates the readOnlyHint annotation, a small redundancy that keeps it short of a 5.

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?

With no output schema and no parameters, the description carries full burden for characterizing the result, and it only gestures at returns ('offers, prices, and the request form URL') without shape, count, or freshness. For a simple read-only lookup this is adequate but leaves the agent guessing about what the payload looks like.

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

Parameters4/5

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

The tool takes zero parameters, which is the baseline-4 case per the rubric. Nothing in the description misleads about inputs, and the empty schema matches the described no-argument retrieval behavior.

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 names a concrete resource (Live Local and Maps offers, prices, request form URL), so an agent knows exactly what comes back. It does not name or contrast with the closely related sibling offer tools (slipvault_offer, starlink_offer, content_offers), so the differentiation is present but implicit via the 'Live Local and Maps' scoping.

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?

It gives a useful negative boundary — 'Does not take an order or a payment' — which tells the agent this is informational only. There is no positive when-to-use guidance and no explicit alternative named for the sibling offer tools, so selection between offers is left to inference.

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