Skip to main content
Glama
Sign In
cobroya

cobroya

by dan1d
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_payments

Find recent payments for your Mercado Pago merchant account. Filter by status to locate specific transactions and manage your payment history.

Instructions

Search recent payments for the authenticated merchant. Supports filtering by status.

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

Input Schema

NameRequiredDescriptionDefault
statusNo
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3/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 burden. It mentions 'recent payments' and 'authenticated merchant', but lacks details on permissions, rate limits, pagination behavior (beyond schema parameters), or what 'recent' means. This is inadequate for a search tool with zero annotation coverage.

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 a single, efficient sentence with no wasted words. It front-loads the core purpose and includes key constraints, making it appropriately sized for the tool's complexity.

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 no annotations, 0% schema description coverage, and no output schema, the description is incomplete. It lacks details on behavioral traits, parameter meanings beyond status, and expected return values, which are critical for a search tool with three parameters.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It only mentions 'filtering by status' for one of the three parameters (status, limit, offset), leaving limit and offset undocumented. This adds minimal value beyond the bare schema.

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 clearly states the verb ('search') and resource ('recent payments for the authenticated merchant'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_payment' or 'create_refund', which might have overlapping domains.

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 implies usage for searching payments with status filtering, but provides no explicit guidance on when to use this tool versus alternatives like 'get_payment' or 'create_refund'. It mentions the authenticated merchant context, which gives some implied context.

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