Skip to main content
Glama

get_person

Retrieves a person’s open commitments in both directions, recent decisions from small meetings together, and shared meetings by person ID or name.

Instructions

One person's open commitments in both directions (what the user owes them and what they owe the user), recent decisions made in small meetings together, and shared meetings.

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": {
      "person": "<person>"
    },
    "name": "get_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
personYesPerson id from list_people, or a name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose real scoping behavior: commitments are limited to open ones, decisions to 'small meetings together', which usefully bounds expectations. But it says nothing about read-only nature (only implied by the get_ prefix), how far back 'recent' reaches, or whether results are paginated or truncated.

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?

One sentence, front-loaded with the resource, and every clause names a distinct content category. It is slightly dense and hard to scan due to the nested parenthetical, but there is no filler.

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 aggregate read with no annotations and no output schema, the description covers the substantive scope of what comes back. The residual gap is the shape of the response (list of meetings vs. summaries, how decisions are represented), which matters somewhat given there is no output schema.

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 parameter is fully documented, including the crucial 'Person id from list_people, or a name' guidance. The description adds nothing about the parameter, so baseline 3 applies.

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 the resource (one person) and enumerates the three things returned: bidirectional open commitments, decisions from small meetings, and shared meetings. That is specific enough to distinguish it from siblings like get_action_items or list_people, though it never states a verb or explicitly contrasts itself with those aggregators.

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?

Usage is only implicit: the enumeration of contents tells an agent this is the per-person dossier for 'what do I owe / what do they owe / what have we decided' questions. There is no when-to-use statement, no exclusions, and no named alternative (e.g. use get_action_items for cross-person lists).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.