Skip to main content
Glama

Answer a plan you were invited to: verdicts and ranks only

ic_plans_guest_answer

For the GUEST of a plan or their assistant. Judge each option against what your person wants and send only a verdict (ok | veto | unknown) and optional rank (1 = best) per option, and ok per time window. Never send reasons, diet, budget or anything else; there is no field for them. The other person sees only the final proposal. Args: { plan_id, token, answer: { options: [{ id, verdict, rank? }], windows?: [{ id, ok }] } }. No auth required.

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": {
      "plan_id": "<plan_id>",
      "token": "<token>",
      "answer": "<answer>"
    },
    "name": "ic_plans_guest_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe guest link token: the t= value in the plan link the guest was sent.
answerYesVerdicts and ranks only. There is no field for a reason: never put preferences anywhere.
plan_idYesThe plan id (pl_...), from ic_plans_create or ic_plans_list.

Output Schema

NameRequiredDescriptionDefault
okNotrue when the call did what it was asked; false with `error` and `error_kind` when it did not
textNoThe tool's reply when it returns plain text instead of JSON
errorNoWhy the call failed, in a sentence a person can act on. Present only when ok is false.
resultNoThe tool's value when it returns a list or a single value instead of an object
error_kindNoMachine-readable failure class: no_token, missing_scope, forbidden, not_found, invalid_input, rate_limited or transient

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "description": "The tool's JSON result. Every field the tool's description names is present at the top level; ok, error and error_kind follow the shared envelope.",
      +  "properties": {
      +    "error": {
      +      "description": "Why the call failed, in a sentence a person can act on. Present only when ok is false."
      +    },
      +    "error_kind": {
      +      "description": "Machine-readable failure class: no_token, missing_scope, forbidden, not_found, invalid_input, rate_limited or transient"
      +    },
      +    "ok": {
      +      "description": "true when the call did what it was asked; false with `error` and `error_kind` when it did not"
      +    },
      +    "result": {
      +      "description": "The tool's value when it returns a list or a single value instead of an object"
      +    },
      +    "text": {
      +      "description": "The tool's reply when it returns plain text instead of JSON"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added
  3. Removed
  4. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the description carries real weight and delivers: 'No auth required' (the token is the credential) and 'The other person sees only the final proposal', which discloses how the write is surfaced to the counterparty. It also warns repeatedly that reasons/diet/budget must never be transmitted because no field exists for them, a genuine behavioral constraint. It omits that the call is non-idempotent and what happens on a duplicate or late submission.

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?

It is short and front-loaded: audience first, then the permitted payload, then the prohibition, then the arg recap. The inline `Args: {...}` duplication of the schema is mildly redundant, and the no-reasons rule is stated twice, but neither bloats the text badly.

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 tool with three top-level parameters, deep nesting, mode-dependent answer shapes and a non-trivial privacy model, the description covers the common case but not the PRIVATE-TIMES / PRIVATE-VENUES variants, which change what must be sent instead of windows or verdicts. An output schema exists, so return values need no explanation, but the mode-branch omission is a real gap for an agent operating on a private plan.

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 schema already documents plan_id, token and every nested answer field, making 3 the baseline. The description adds the verdict/rank vocabulary and the privacy prohibition, but its `Args` recap mentions only `options` and `windows` while silently omitting the psi, psi_venues, common_options and common_windows branches that actually distinguish plan modes; a reader of the description alone would think the answer is always verdicts plus windows.

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 names a specific verb (judge/answer), a specific resource (a plan the agent's person was invited to), and the exact audience ('the GUEST of a plan or their assistant'), plus the exact payload shape (verdict + optional rank per option, ok per window). It does not, however, distinguish itself from the close siblings ic_plans_guest_get and ic_plans_guest_respond, so an agent must infer the boundary from names alone.

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?

It establishes the guest side of the exchange ('For the GUEST ... or their assistant') and implicitly excludes the owner-side fields, which is useful routing context. But there is no explicit when-to-use/when-not guidance relative to ic_plans_guest_get (read the plan first?) or ic_plans_guest_respond, and no statement about whether answering can be revised later.

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.