Skip to main content
Glama

Bettiz Legal — guías legales (Chile)

Buscar guías legales publicadas

search_guides
Read-onlyIdempotent

Busca entre las guías y servicios publicados por Bettiz Legal (estudio jurídico en Santiago, Chile) sobre derecho inmobiliario y arriendos, empresas y pymes, y herencias: posesión efectiva, testamentos, juicios de arriendo, precario, gastos comunes, SpA, pactos de socios y otros. Devuelve título, resumen, enlace y fecha de revisión. Solo lectura; información general, no asesoría legal. No escribas datos personales ni detalles de un caso en la búsqueda: usa el tema.

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": {
      "query": "<query>"
    },
    "name": "search_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNo
limitNo
queryYesTema, p. ej. «posesión efectiva», «arrendatario no paga», «constituir SpA»

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 declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is largely covered. The description still adds real value beyond them: the disclaimer that results are general information and not legal advice, the explicit privacy rule against submitting case details, and the returned fields (título, resumen, enlace, fecha de revisión) in the absence of an output schema.

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 description is front-loaded with purpose, then returns, then compliance notes, and every sentence carries operational value. The long topic enumeration is dense but serves retrieval matching; minor trimming of 'y otros' style fillers would tighten it further.

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 3-parameter read-only search with no output schema, the definition covers purpose, domain, return shape, legal disclaimer and query privacy. Only the 'limit' parameter and any default/pagination behavior remain undocumented, a small residual gap.

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 only 33%, so the description must compensate, and it largely does: the query parameter is given concrete example phrasings and an explicit constraint against personal data, and the domain topics listed map naturally onto the 'area' enum values. Only 'limit' (default, pagination behavior) is left entirely to 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?

The description names a specific verb ('Busca') and a concrete resource ('guías y servicios publicados por Bettiz Legal'), scoped to three legal domains with example topics (posesión efectiva, precario, SpA). This makes the tool's function unmistakable, though it never explicitly contrasts itself with siblings like list_services or get_page.

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 privacy instruction ('No escribas datos personales... usa el tema'), which tells the agent how to phrase a query. However, there is no explicit statement of when to choose this over get_page, how_to_book or list_services.

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