Skip to main content
Glama

Listar comercios

listar_comercios
Read-only

Lists platform merchants with their payment processor and current status, enabling MCP clients to retrieve merchant details and verify account state.

Instructions

Lista los comercios de la plataforma, con su procesador y estado.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes this is a safe read, so the description's main added value is telling the agent what fields come back (processor and status). It says nothing about volume, pagination, ordering, or whether the list is scoped to the caller's account — gaps that matter for an unfiltered full-list call.

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?

A single short sentence with the resource front-loaded and the returned fields appended; nothing is redundant or buried. It is sized appropriately for a trivial zero-argument list tool.

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 no-parameter read tool with an explicit readOnlyHint and no output schema, the description covers what the tool is and roughly what it returns. It falls short on result scope — an agent cannot tell whether this returns the entire merchant catalog or a bounded page.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies no filtering arguments are needed to call it.

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?

"Lista los comercios de la plataforma" gives a specific verb (list) and resource (merchants), and adds that each entry carries its processor and status. The resource name distinguishes it from the sibling list tools (links, pagos), though the description never names an alternative explicitly.

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 statement of when to use this tool versus the other listing tools, no preconditions, and no indication of whether the list is complete or paginated. Usage is only inferable from the resource name, which is the minimum implied-usage case rather than real guidance.

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