Skip to main content
Glama

Read a plan you were invited to, with its link token

ic_plans_guest_get
Read-only

For the GUEST of a plan, or the guest's own AI assistant. NO IC ACCOUNT NEEDED: the t= token from the plan link is the credential, and a wrong token answers not_found exactly as a missing plan does. Returns the options, windows, your own answer, the current proposal and next_step; never the other side's answer. Args: { plan_id, token }. 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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe guest link token: the t= value in the plan link the guest was sent.
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.2/5.0
Behavior5/5

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

Goes well past readOnlyHint/openWorldHint by disclosing the auth model (the link token IS the credential, no account required) and the error semantics ('a wrong token answers not_found exactly as a missing plan does'), which tells the agent not to treat not_found as proof the plan never existed. It also discloses a data-scoping rule — your own answer and the current proposal are returned, 'never the other side's answer' — which is exactly the kind of behavior an annotation cannot express.

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-loaded with the audience and the credential model before the return-shape detail, which is the right order for an agent skimming. The 'Args: { plan_id, token }' fragment is redundant against the schema and could be cut, but overall the text is dense with no wasted sentences.

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 the brief return listing is optional; the critical unknowns for a low-complexity, 2-param read tool — auth, error behavior, and visibility scoping — are all covered. Remaining gaps are minor, such as what happens with an expired or revoked link versus a wrong one, and whether the token can be reused.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns one more by characterizing token as the auth credential and showing the shape as { plan_id, token }, reinforcing that both are mandatory to authenticate. It adds no format detail beyond that, so not a 5.

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?

Names a specific verb and resource ('Read a plan you were invited to, with its link token') and pins the audience ('For the GUEST of a plan, or the guest's own AI assistant'), which separates it from the authenticated plan tools. It does not explicitly name the write-side siblings (ic_plans_guest_answer / ic_plans_guest_respond) as the place to submit an answer, so differentiation is implied rather than stated.

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 clear conditions for use: you are a guest of the plan, you have the t= link token, and no IC account exists. What is missing is an explicit exclusion — e.g. that authenticated owners should use the non-guest plan tools, or that this is read-only and the guest must call the answer tool to submit.

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.