Skip to main content
Glama
Sign In

Adónde

by com.getadonde
OverviewDiscussionsAdmin

Hold a card request

stage_intent
Read-only

Called by Adonde's cards when a button is pressed, not by the assistant. Holds that button's exact arguments for 30 minutes under a short code and returns it as ref; the matching tool loads them when called with that intent_ref. Changes no trip and sends nothing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>"
    },
    "name": "stage_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNoThat tool's arguments, for one call.
kindYesThe tool the button asks for.
callsNoSeveral calls of that tool, e.g. one edit_day per day.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds substantive behavior beyond annotations: a 30-minute expiry, a returned ref, and no side effects. The 'changes no trip and sends nothing' clause reinforces readOnlyHint without merely repeating it. It could say more about collision or expiry behavior, but the essential traits are clear.

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?

Two tightly packed sentences, front-loaded with the caller constraint and followed by the staging behavior. Every clause carries useful information.

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?

With no output schema, the description correctly explains the return value as a short-code ref and how the matching tool consumes it. It covers the key operational context for a read-only staging tool. Minor behavioral edge cases are left implicit.

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 description coverage is 100%, so the baseline is 3. The description reinforces that args are the button's exact arguments and that a ref is returned, but it does not add meaning to kind, args, or calls beyond what the schema already documents.

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 action: holds a card button's arguments for 30 minutes under a short code and returns a ref for a matching tool to load. It distinguishes itself from all execution siblings by emphasizing that it only stages arguments and changes nothing.

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?

Explicitly says it is called by Adonde's cards, not by the assistant, which is a clear exclusion. It does not name what the assistant should use instead, but the intended caller and boundary are unmistakable.

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

All Adónde toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources