Skip to main content
Glama

Open an invitation

open_invitation
Read-onlyIdempotent

Open an invitation a business sent the user, using the invitation code from their message (8 letters and digits, e.g. K7Q2M8XD). Returns the business, what the invitation is about, its contact person and its current public documents with download links. Works before the user signs in. Documents shared only with the invited address open after that address confirms the invitation (the claim link in the result) and signs in.

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": {
      "code": "<code>"
    },
    "name": "open_invitation"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe invitation code, e.g. K7Q2M8XD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, which already indicate read-only, idempotent, non-destructive, closed-world behavior, the description adds important operational details: the call works before authentication, returns a claim link, and gates address-specific documents behind confirmation and sign-in. These are meaningful behavioral traits that an agent would not know from the annotations alone.

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?

The description is front-loaded with the core action and code requirements, then adds return-value context and the sign-in/document-claim nuance. Every sentence carries useful information and there is no redundant wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema, the description explains what the tool returns: the business, invitation subject, contact person, and public documents with download links. It also covers the authentication and document-access edge case, making the definition complete for an agent to call it correctly.

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 single parameter is already fully documented. The description reinforces the expected format and source of the code, but adds little semantic detail beyond what the schema and annotations provide. A baseline score of 3 is appropriate.

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?

The description states a specific verb and resource: opening an invitation a business sent the user, using the invitation code. It clearly distinguishes the action from sibling tools like get_documents or status by describing the invitation-opening workflow and its returned context.

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?

The description gives clear usage context: the code comes from the user's message, it works before sign-in, and documents requiring the invited address open only after confirmation. It does not explicitly name alternatives or state when not to use it, but the invocation context is well established.

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