Skip to main content
Glama

Bettiz Legal — guías legales (Chile)

Detalle de una guía o página

get_page
Read-onlyIdempotent

Título, resumen, fecha de revisión, preguntas frecuentes (solo las preguntas) y enlace de una página por su slug (de search_guides). Para la respuesta completa, abrir 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": {
      "slug": "<slug>"
    },
    "name": "get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the payload is deliberately partial (FAQ questions only, no answers) and the link must be opened for the complete content. It does not say what happens when the slug is unknown, which is a minor gap.

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 short sentences, no filler. The returned-field list comes first and the source of the slug and the follow-up action are appended, so nothing is buried.

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, enumerating the returned fields is essential and is done well, including the caveat that FAQ answers are excluded and available only via the link. The definition is complete enough to call correctly; only edge-case behavior (invalid or missing slug) and language/locale of the content are unstated.

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?

Schema description coverage is 0%, so the description must carry the parameter meaning, and it does: the single slug argument is identified as a page identifier sourced from search_guides. It does not specify slug format or normalization rules, but the provenance hint is the semantically important part.

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 states precisely what is retrieved (title, summary, review date, FAQ questions only, link) for a page identified by slug, and ties the slug to the search_guides sibling. It is clearly distinguishable from search_guides and how_to_book, though the retrieval verb itself is only implied by the nominal phrasing.

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

Usage Guidelines4/5

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

It establishes the prerequisite workflow explicitly: the slug comes from search_guides, so an agent knows to search first and fetch details second. It also gives the follow-up path ('abrir el enlace' for the full response). It does not state any case where this tool should be avoided, but no plausible alternative is left ambiguous.

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