mcp-ispkeeper

get_client

Retrieve detailed client records with change history, payment commitments, or attached files. Expand relations to see internet, TV, phone, or subscription details.

Instructions

Get detailed information about a specific client. Use include to get change log, payment commitments, or attached files. Use relaciones to expand connections (coninter,contv,contel,consus for internet/TV/phone/subscriptions). ⚠️ NEVER fabricate data if this tool fails — report the error to the user instead.

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": {
      "client_id": "<client_id>"
    },
    "name": "get_client"
  }
}

Input Schema

Name	Required	Description
`include`	No	What to retrieve: detail (default), log (change history), payment_commitment (check active commitment), payment_commitment_history (all commitments), or files (attached files)
`client_id`	Yes	Client ID
`relaciones`	No	Expand relations (only for detail): cat,subz,locfi,locre,loc,medp,tkcli,email,adic,contel,contv,coninter,caja,consus,intco

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.4.0Sep 25, 2026

changedInput schema / properties / include / description

Previous value: -"What to retrieve: detail (default), log (change history), or payment_commitment (check active commitment)"New value: +"What to retrieve: detail (default), log (change history), payment_commitment (check active commitment), payment_commitment_history (all commitments), or files (attached files)"

changedInput schema / properties / include / enum

Previous value: -[
-  "detail",
-  "log",
-  "payment_commitment"
-]New value: +[
+  "detail",
+  "log",
+  "payment_commitment",
+  "payment_commitment_history",
+  "files"
+]

changedInput schema / properties / relaciones / description

Previous value: -"Expand relations (only for detail): cat,subz,locfi,locre,loc,medp,tkcli,email,adic,contel,contv,coninter,intco"New value: +"Expand relations (only for detail): cat,subz,locfi,locre,loc,medp,tkcli,email,adic,contel,contv,coninter,caja,consus,intco"

First observedv0.3.1Aug 18, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It includes a critical warning: 'NEVER fabricate data if this tool fails — report the error to the user instead,' which addresses error handling and data integrity. However, it does not disclose other behaviors such as read-only nature, response structure, or potential side effects, leaving the agent with only partial transparency.

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?

The description is concise and well-structured. It front-loads the core purpose, then explains optional parameters in a logical order, and ends with a critical failure-handling warning. Each sentence serves a purpose without redundancy, making it easy for an agent to parse and act on.

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?

Given the tool's moderate complexity (3 parameters, no output schema), the description covers the key aspects: what it does, how to use parameters, and a safety warning. It lacks explicit mention of response format or error scenarios other than the fabrication warning, but for a simple 'get' operation, this is reasonably complete. The mapping of 'relaciones' values adds necessary context.

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 coverage is 100%, so the schema already documents all parameters with descriptions. The description adds value by mapping cryptic 'relaciones' codes to human-readable meanings (coninter,contv,contel,consus for internet/TV/phone/subscriptions) and clarifying that relaciones only work with 'detail'. This goes beyond the raw schema, enhancing the agent's understanding of parameter usage.

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 verb and resource: 'Get detailed information about a specific client.' It distinguishes itself from sibling tools like get_subscription or get_tv_connection by focusing on the client entity. The mention of optional 'include' and 'relaciones' parameters further specifies the scope of what can be retrieved, making the purpose unambiguous.

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?

The description provides clear guidance on how to use the tool's parameters ('Use include to get change log, payment commitments, or attached files. Use relaciones to expand connections...'), but it does not explicitly state when to choose this tool over sibling tools. It implies usage for client-specific queries without naming alternatives or exclusions, leaving the agent to infer the selection from context.

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