Skip to main content
Glama

List my arrangements

evuun_list
Read-onlyIdempotent

This person's arrangements, newest first, each with its stage and what is needed from them. Through this host only, unless they signed in to EVUUN (then all of them). Open one with evuun_open.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description earns credit for going beyond them: result ordering (newest first), per-item contents (stage, what is needed), and the important caveat that results may be limited to this host unless the person signed in to EVUUN. It says nothing about pagination, default result count, or whether 'limit' truncates the newest or oldest end.

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?

Three tight sentences, each doing work: what is returned, the host-scope caveat, and the next step. Front-loaded ordering and item shape before the caveat. Minor terseness ('This person's arrangements' is a fragment) but no padding.

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 low-complexity read-only list with rich annotations and no output schema, most needs are met. The gap is the single parameter: neither schema nor description explains limit's effect or default, so the agent cannot control result volume knowingly.

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% and the only parameter (limit, 1-50) is never mentioned in the description. 'Newest first' hints at how truncation would behave, but the agent is not told what limit does, what the default is, or how to page. With a 1-param tool whose schema carries no prose, the description should compensate and does not.

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?

Concrete resource with scope: 'This person's arrangements, newest first, each with its stage and what is needed from them' states ordering and the shape of each item. The verb is implicit (title supplies 'List'), but an agent can immediately tell this is the personal-arrangements listing. It is not explicitly differentiated from siblings like evuun_find.

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

Usage Guidelines4/5

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

Gives real routing context: the host-scoping rule ('through this host only, unless they signed in to EVUUN') and a follow-up path ('Open one with evuun_open'). There is no explicit exclusion telling the agent when to prefer evuun_find or evuun_watch instead, so it is strong context rather than full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources