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

mcp-bd-readonly

by noemartinezoptima
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

remesas_pendientes

Retrieve pending remittances sorted by due date, limited to max_n, and return the total for financial reporting.

Instructions

Efectos pendientes (últimos por vencimiento, max_n límite) y total

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

Input Schema

NameRequiredDescriptionDefault
max_nNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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, and it does disclose some behavior: results are ordered by due date and an aggregate total is included. It says nothing about read-only safety, permissions, pagination beyond max_n, or what the total represents, so coverage is only partial.

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 parenthetical covering ordering, limit, and total — front-loaded with no filler. It is terse to the point of under-specification, but nothing is wasted.

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?

For a simple one-parameter list tool with no output schema and no annotations, the description conveys the essentials (what is returned, ordering, cap, total). It is still silent on usage context and the meaning/safety of the operation, leaving moderate gaps.

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 0% for the single parameter, but the description does explain its role by labeling max_n as a limit on returned items. That is useful, though the schema's title 'Max N' and default of 50 already convey most of this, so added value is marginal.

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

Purpose3/5

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

The description names a specific resource ('Efectos pendientes') and states the ordering and the aggregated total it returns, so the agent can infer it is a pending-items listing. However, there is no explicit verb and nothing that distinguishes it from related siblings such as conciliar_remesas, so purpose is only partially pinned down.

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?

There is no when-to-use or when-not-to-use guidance, and no sibling is named as an alternative despite several closely related tools (conciliar_remesas, facturas_venta, excepciones) in the toolset. The agent must infer usage context entirely from the tool name.

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