Skip to main content
Glama
Sign In
mcp-bd-readonly

mcp-bd-readonly

by noemartinezoptima
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cuadre_factura

Verifies that an invoice's line-item sum equals its header total, helping detect billing discrepancies in read-only invoicing data.

Instructions

Comprueba que la suma de líneas == total de cabecera

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": {
      "factura_id": "<factura_id>"
    },
    "name": "cuadre_factura"
  }
}

Input Schema

NameRequiredDescriptionDefault
factura_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It confirms a validation action but does not state whether the tool is read-only, what permissions are needed, what it returns, or how failures are reported.

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 front-loaded sentence with no wasted words. It is appropriately terse, though its brevity reflects missing detail rather than strong conciseness.

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?

For a one-parameter validation tool with no annotations or output schema, the description is incomplete. It states the check but omits parameter meaning, return behavior, and any operational context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and there is one parameter, factura_id, which the description never mentions. It does not explain what the parameter identifies or how it should be supplied, so it fails to compensate for the schema gap.

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?

States a specific verb (Comprueba) and validation rule (suma de líneas == total de cabecera), so the agent can understand what the tool does. It does not distinguish this tool from siblings such as facturas_venta or resumen_iva, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives no explicit guidance on when to use this tool versus alternatives. The purpose implies it is for invoice consistency checking, but there is no when/when-not context or routing to sibling tools.

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