Skip to main content
Glama

list_people

Find people you meet by name, meeting history, and open-action counts. Review contacts from calendar attendees, speaker names, and action owners; email addresses are not returned.

Instructions

List people the user meets, joined from calendar attendee names, speaker names applied in LokalBot, and action owners. Returns names, meeting counts, last meeting, and open-action counts in each direction. Email addresses are never returned.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum people (default 50, maximum 200).
queryNoOptional name substring.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does contribute real value by disclosing the extracted fields and a privacy guarantee ('Email addresses are never returned'), but it omits ordering, whether results are truncated, and any permission requirements for a tool aggregating calendar and bot data.

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?

Three tight sentences, each earning its place: source description first, return shape second, privacy constraint last. Front-loaded and free of 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 two-optional-parameter list tool with no output schema, the prose adequately covers what comes back (names, meeting counts, last meeting, open-action counts per direction) and what does not (emails). Only ordering and truncation behavior remain unstated.

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 'limit' and 'query' are already fully documented including the default of 50 and max of 200. The description adds no parameter meaning beyond the schema, which is the baseline case for full coverage.

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?

States a concrete verb (list) plus resource (people), and goes further by naming the exact data sources joined (calendar attendees, LokalBot speaker names, action owners). This distinguishes it from the singular get_person sibling without needing the schema.

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 implied by 'people the user meets' and by disclosing the returned fields, so an agent can infer this is a browse/discovery call. However, there is no explicit when-to-use versus get_person, no exclusions, and no statement about ordering or paging behavior to guide invocation.

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