Skip to main content
Glama

Accept or pass on the proposal of a plan you were invited to

ic_plans_guest_respond

For the GUEST of a plan or their assistant: accept or pass on the current proposal, or leave the plan (leave:true, which ends it). ASK YOUR PERSON FIRST, it commits them. Both sides accepting confirms the plan; passing moves to the next proposal and says nothing about why. Args: { plan_id, token, accept?: boolean, leave?: boolean }. 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>"
    },
    "name": "ic_plans_guest_respond"
  }
}

Input Schema

NameRequiredDescriptionDefault
leaveNotrue leaves the plan, which ends it for both.
tokenYesThe guest link token: the t= value in the plan link the guest was sent.
acceptNotrue accepts the current proposal, false passes.
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

A4.1/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: the commitment nature of acceptance, that both sides accepting confirms the plan, that passing silently advances and gives no reason, that leave ends the plan for both, and that no auth is required (the token is the credential). Only mild tension exists with destructiveHint=false given that leave:true terminates the plan for both parties; that is disclosed rather than contradicted, so no flag.

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?

Front-loads the audience and action, then consequences, then the parameter line — a sensible order for an agent. The inline 'Args: { ... }' block duplicates the input schema and is the one sentence that does not fully earn its place.

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?

An output schema exists, so return values need no explanation, and the description covers actor, auth model, and the consequence of each branch. It leaves unstated the required plan/proposal state (e.g. whether a proposal must be pending) and error behavior for an expired token, which are the remaining gaps for a state-mutating tool.

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 schema already defines plan_id, token, accept and leave in comparable detail. The description's 'Args: {...}' restates the schema and adds only a little meaning (that passing gives no reason), 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?

Opens with an explicit audience and action: 'For the GUEST of a plan or their assistant: accept or pass on the current proposal, or leave the plan.' The three outcomes (accept / pass / leave) are each named, so an agent can distinguish this from ic_plans_guest_answer or ic_plans_guest_get without opening a schema.

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?

States the actor who should call it and the effect of each option, plus a strong pre-condition ('ASK YOUR PERSON FIRST, it commits them'), which effectively tells the agent to confirm before invoking. It stops short of naming a sibling alternative or an explicit when-not-to-call condition, so it is clear context rather than full routing 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.