Skip to main content
Glama

Estimate when a TIE card is ready

tiehoy_lote_estimate
Read-onlyIdempotent

Whether a TIE card with a given lote number is ready for pickup at a specific office. The expected pickup window, its basis and the progress chart are on the linked tiehoy.com page.

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>",
      "office": "<office>",
      "lote_number": "<lote_number>"
    },
    "name": "tiehoy_lote_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the returned page links. Default en.
officeYesOffice name or part of it. If several match, the tool lists them.
provinceYesSpanish province of the office.
lote_numberYesThe lote number (0–999) printed on the fingerprint receipt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), and the description adds genuinely useful context: results are expressed as an expected pickup window with its basis, plus a progress chart delivered on a linked tiehoy.com page. That tells the agent the return value is partly a link rather than structured data, which annotations cannot convey. It stops short of describing not-found or error behavior.

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?

Two sentences with no filler: the first states the question answered, the second states what the caller gets back. The essential scope is front-loaded and nothing is repeated from the schema.

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 explaining returns and does so adequately by naming the pickup window, its basis, and the progress chart on the linked page. It is slightly thin on what happens when the lote is not found or when several offices match, though the schema covers the latter.

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 province, office, lote_number and lang are already documented in the schema, including the office-name partial-match and listing behavior. The description adds no syntax, format, or edge-case meaning beyond that, so the baseline of 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 concrete resource (TIE card lote number) and a concrete outcome (readiness for pickup at a specific office), so the agent knows exactly what question this tool answers. It does not, however, contrast itself with the sibling tiehoy_lote_status, leaving the boundary between 'estimate' and 'status' implicit.

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 implied by the nature of the question — 'is my card ready yet' — but there is no explicit when-to-use or when-not-to-use guidance and no mention of the sibling alternative. An agent can guess the intent but must infer the choice between this and tiehoy_lote_status.

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