Skip to main content
Glama

TIE card lote status

tiehoy_lote_status
Read-onlyIdempotent

Current TIE (foreigner identity card) pickup lote for a Spanish province: the latest lote released at each police office, lotes released this week and last week, the 3-week weekly average, and when it was observed. Optionally filter to one office by name. Returns page links on tiehoy.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": {
      "province": "<province>"
    },
    "name": "tiehoy_lote_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the returned page links. Default en.
officeNoOptional office name or part of it, e.g. "Poblados" or "Rambla Guipúzcoa".
provinceYesSpanish province, e.g. Madrid, Barcelona, Valencia, Alicante.

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is settled. The description adds genuinely new context: the exact set of values returned (including the 3-week weekly average and when the data was observed) and the fact that the response consists of page links on tiehoy.com, which explains the lang parameter's relevance. It stops short of describing freshness guarantees or pagination beyond 'page links'.

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 core purpose is front-loaded in the first clause, and the enumerated return values are packed into one sentence rather than bloating into paragraphs. The trailing 'Returns page links on tiehoy.com' sentence earns its place by clarifying the output form, though the return-value list could be tightened.

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?

With no output schema, the description carries the burden of describing the return payload and does so concretely: per-office latest lote, week-over-week lotes, 3-week average, and observation timestamp. Combined with annotations covering safety and a fully documented schema, an agent has what it needs to call it, with the only gap being how the sibling estimate tool differs.

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%, with all three parameters documented and examples supplied (Poblados, Rambla Guipúzcoa; Madrid, Barcelona...). The description restates the office filter as 'optionally filter to one office by name' and hints that lang governs the page links, but adds no syntax or matching semantics beyond the schema, 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 description names a specific resource and scope: the current TIE pickup lote for a Spanish province, and enumerates what is returned (latest lote per office, this week, last week, 3-week average, observation time). It is clear what the tool does, but it never distinguishes itself from the sibling tiehoy_lote_estimate, so an agent cannot tell from the description alone which of the two to pick.

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 by the scoping language (a Spanish province, optionally narrowed to one office by name). There is no explicit statement of when to use this versus tiehoy_lote_estimate, and no exclusions or preconditions are given, leaving the agent to infer the boundary.

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