Skip to main content
Glama

Buscar en las guías de UK sin filtro

buscar_guia
Read-onlyIdempotent

Busca en los artículos y guías gratis de UK sin filtro (en español) sobre dinero y trámites en UK: llegar a UK, nómina y payslip, tax code de emergencia, Income Tax y National Insurance, NI number, council tax, alquiler y depósito, ISA, pensión de empresa, historial de crédito, Hacienda española si vives en UK y mandar dinero a España. Devuelve el texto relevante y el enlace.

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": {
      "tema": "<tema>"
    },
    "name": "buscar_guia"
  }
}

Input Schema

NameRequiredDescriptionDefault
temaYesQué quieres saber, p. ej. "cómo pedir el NI number" o "acabo de llegar, qué hago primero".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / tema / description
      Previous value: -"Qué quieres saber, p. ej. \"cómo pedir el NI number\" o \"descuento council tax\"."New value: +"Qué quieres saber, p. ej. \"cómo pedir el NI number\" o \"acabo de llegar, qué hago primero\"."
  2. 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 covered. The description adds the return behavior ('Devuelve el texto relevante y el enlace'), which is useful, but says nothing about result count, ranking, or whether a query with no matches returns empty vs. fallback content.

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?

One front-loaded sentence leading with the verb and resource, followed by a topic enumeration that doubles as scope documentation. The list is long but each item conveys a real coverage area; only the parenthetical 'sin filtro (en español)' is slightly clunky.

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 simple one-parameter, read-only search tool with full schema coverage and clear annotations, the description covers purpose, domain, and return shape. It does not explain what an empty result looks like, but nothing else an agent needs to invoke it correctly is missing.

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 parameter already has a description with example queries, so the baseline is 3. The description adds only that the search is 'sin filtro' in Spanish, which implies free-text natural-language input but gives no extra syntax or formatting guidance beyond the schema.

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?

States a specific verb and resource ('Busca en los artículos y guías gratis de UK'), plus a scope qualifier ('en español', 'sin filtro') and an explicit topic list covering money and paperwork. An agent can tell this is an informational search tool rather than a calculator, though the distinction from the 'recursos' sibling is left 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 topic enumeration and the 'sin filtro' framing — use it for open informational questions — but there is no explicit when-to-use or when-not-to-use statement and no named alternative (e.g., calcular_nomina or recursos) for queries that fit those siblings instead.

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