Skip to main content
Glama

mapumi Wunschzettel und Einladung

Read party and answers

get_party
Read-only

With the edit link: the party and every guest with their answer (yes, no or open), allergies, siblings and pickup, plus counts. With a guest link: that guest's own invitation only.

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": {
      "link": "<link>"
    },
    "name": "get_party"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesParty edit link or guest link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: the result scope differs sharply by link type, and a guest link deliberately exposes only that guest's own invitation, which is a privacy-scoping trait an agent needs to know before calling. It omits error behavior for malformed links and says nothing about pagination or size of large parties.

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 sentences, each doing distinct work, with the mode split front-loaded as parallel clauses ('With the edit link... With a guest link...'). There is no filler, hedging, or restated title text, and the most decision-relevant fact — which link type produces which scope — comes first.

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?

For a one-parameter read-only tool with no output schema, the description carries the necessary burden well by enumerating the returned fields for the edit-link case and stating the limited scope for the guest-link case. The guest-link branch is comparatively vague ('that guest's own invitation only'), and no error or edge-case behavior is covered.

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% and the single 'link' parameter is already documented as 'Party edit link or guest link', so the baseline is 3. The description does add meaning by explaining the consequence of each link type, but it gives no format, validation, or expiry detail beyond the schema's own wording, so it does not clear the baseline by much.

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 read operation and enumerates exactly what comes back in each mode: party plus every guest with answer (yes/no/open), allergies, siblings, pickup and counts for the edit link, versus a single invitation for a guest link. That is far more than a restatement of the name. It stops short of a perfect 5 because it never names a sibling tool or explicitly contrasts itself with readers like get_wishlist.

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?

Usage is framed as a branch on the caller's input: an edit link yields the whole party, a guest link yields only that guest's invitation. That tells an agent which link to supply and what it will get, which is the operative decision here. There is no explicit 'use X instead' routing or statement of failure conditions for an invalid/expired link, so it is not a 5.

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