Skip to main content
Glama
Sign In
mcp-pedidos

mcp-pedidos

by lucabaello1998
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

listar_pedidos

Lists orders visible to the current session, newest first, with optional status filtering to help customers or business owners review order history.

Instructions

Lista los pedidos visibles para esta sesión, del más nuevo al más viejo. Un cliente ve solo los suyos; el dueño del negocio ve todos. Se puede filtrar por 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_pedidos"
  }
}

Input Schema

NameRequiredDescriptionDefault
estadoNoFiltra por estado del pedido.
limiteNoCuántos pedidos devolver (1 a 100, por defecto 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does deliver key behavior: deterministic ordering (newest first), role-based result scoping (customer vs. business owner), and filterability. It stops short of describing the default result cap or whether results are paged, which it leaves entirely to the schema.

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?

Three short sentences, front-loaded with what is listed and how it is ordered, followed by visibility scoping and filtering. No filler or repetition of the schema.

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?

For a simple two-optional-parameter read tool with no output schema, the description covers ordering, visibility rules and filtering, which is most of what an agent needs. The only gap is result-volume behavior (pagination beyond the schema's default limit), a minor omission here.

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 100%, so the enum values for 'estado' and the 1-100 range/default for 'limite' are already fully documented. The description mentions only the status filter and adds no format or behavior detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Lista los pedidos') plus scope ('visibles para esta sesión') and ordering ('del más nuevo al más viejo'). An agent can tell this is a bulk listing operation, distinct from the singular 'consultar_pedido' sibling, without opening the schema.

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 explains who sees what ('un cliente ve solo los suyos; el dueño ve todos') and that filtering by status is possible, which implies when to use it. However, it never names an alternative such as fetching a single order or the summary tool, and gives no explicit when-not guidance.

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