Skip to main content
Glama

Bettiz Legal — guías legales (Chile)

Áreas y servicios del estudio

list_services
Read-onlyIdempotent

Áreas de práctica, tipos de cliente y páginas de servicio de Bettiz Legal, y cómo se cobra el primer paso (sin montos).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_services"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 one useful behavioral fact — the result deliberately excludes monetary amounts — but says nothing about the shape or size of what comes back.

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?

A single compact sentence with the content scope front-loaded and no filler. The trailing billing clause is slightly ambiguous in phrasing ('cómo se cobra el primer paso') but still earns its place as a scope marker.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no parameters, the description is the only source of information about the response, and it conveys the topics covered but not the granularity or structure (e.g. whether entries include URLs or identifiers). Adequate for a simple read-only listing, but leaves an avoidable 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?

There are zero parameters, so there is no parameter meaning to add; the baseline for a no-param tool applies. The description correctly implies a single unfiltered enumeration rather than a searchable resource.

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 concrete content: practice areas, client types, service pages, and how the first step is billed. That is a specific resource scope an agent can match to a request, though it never explicitly contrasts itself with siblings like get_page or how_to_book.

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?

No explicit when-to-use statement or named alternative. The parenthetical '(sin montos)' functions as an implicit negative constraint — don't call this for actual pricing figures — but the agent must infer the rest of the routing decision.

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