Skip to main content
Glama
Sign In
zyta-sign-mcp

zyta-sign-mcp

by blanck1945
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Listar documentos

kairo_list_documents

Lists visible documents for a user token, respecting study rules for owners, partners, and lawyers.

Instructions

Lista los documentos visibles para el usuario del token, respetando reglas de Estudio (owner/socio/abogado).

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

Input Schema

NameRequiredDescriptionDefault
limitNoCantidad máxima de docs a devolver (default 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It adds behavioral context by mentioning role-based rules, but does not disclose authentication needs, rate limits, or pagination behavior beyond the limit parameter.

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 a single clear sentence with no wasted words. It is front-loaded with the main action and quickly adds context. Slightly more structure (e.g., mentioning output) could improve it, but it's effective as is.

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

Completeness2/5

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

Given the simple input schema (only limit) and no output schema, the description should explain what the returned documents contain (e.g., fields like name, status). It only says 'lists documents' without specifying output details, leaving the agent uncertain.

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?

The schema already describes the limit parameter with default and range. The description adds no additional semantic value beyond what is in the schema, so a baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists documents visible to the token user, respecting studio roles (owner/socio/abogado). It uses a specific verb-resource pair and distinguishes from siblings like get_document or upload_document.

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?

The description implies usage context by stating role-based visibility, but does not explicitly say when to use this tool over other list tools or provide exclusions. However, the purpose is clear enough for an agent to infer appropriate use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools