Skip to main content
Glama

Servicios de MisCausas

listar_servicios
Read-onlyIdempotent

Lista los servicios legales de MisCausas.cl (insolvencia y deudas en Chile, Ley 20.720) por audiencia: personas, empresas, acreedores, trabajadores y compradores de activos. Incluye la página de cada servicio y su honorario «desde» cuando el estudio lo publica.

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": "listar_servicios"
  }
}

Input Schema

NameRequiredDescriptionDefault
audienciaNoFiltra por audiencia. Sin este argumento se listan todas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive and closed-world behavior, so the description's job is to add context. It does so by disclosing payload contents (each service's page plus its 'desde' fee) and by flagging conditional presence ('cuando el estudio lo publica'), which tells the agent some fee fields may be absent.

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, front-loaded with the verb and resource, then the audience axis, then return content. No filler, no restatement of the title beyond what is needed, and the domain qualifier is parenthetically contained.

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

Completeness5/5

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

This is a simple one-parameter list tool with a fully described schema and no output schema, and the description volunteers what the results contain plus the conditional-fee caveat. Nothing an agent needs in order to call it and interpret the response 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 enum parameter is fully documented, including the 'no argument = all audiences' fallback. The description repeats the enumeration but adds no syntax, ordering or filtering nuance beyond the schema, 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 gives a specific verb and resource ('Lista los servicios legales de MisCausas.cl'), scopes the domain (insolvencia y deudas, Ley 20.720) and enumerates the audience buckets. It does not explicitly contrast itself with siblings like consultar_precios, even though fee data ('honorario desde') overlaps with that name, so an agent must infer the boundary.

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 only implied: it is clearly a browsing/enumeration tool, and the audience axis suggests when a filter applies. There is no explicit when-to-use vs. when-to-use-another-tool guidance and no exclusions, leaving the agent to infer that this is the entry point before consultar_precios or evaluar_situacion.

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