Skip to main content
Glama

Open promises

list_commitments
Read-onlyIdempotent

Retrieve open promises from recorded meetings, split into what you owe and what others owe you. Filter by person, project, team, or overdue items to track outstanding commitments.

Instructions

Open promises from recorded meetings, newest first, in two lists: 'mine' (what the user owes) and 'waiting_on_others' (what others owe the user); finished ones are left out. Use for "what do I owe", "what is overdue", "what is Anna still waiting on". For one colleague's whole picture use get_person; to get a name's exact spelling first, list_people.

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_commitments"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost items in each of the two lists. Default 50; older promises past the limit are left out.
personNoOnly promises owned by this person: the exact name as list_people returns it, case-insensitive. Omit for everyone.
projectNoOnly promises from meetings filed under this project id, from list_projects.
team_onlyNoOnly promises made by the user's direct reports (people marked "Reports to me" in Griasa). For "what does my team owe me".
overdue_onlyNoOnly promises past their due date.

Output Schema

NameRequiredDescriptionDefault
mineNo
waiting_on_othersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / team_only
      Added value: +{
      +  "description": "Only promises made by the user's direct reports (people marked \"Reports to me\" in Griasa). For \"what does my team owe me\".",
      +  "type": "boolean"
      +}
  2. Changed3 schema fields changedv1.0.22
    • changedInput schema / properties / limit / description
      Previous value: -"Most items per list. Default 50."New value: +"Most items in each of the two lists. Default 50; older promises past the limit are left out."
    • changedInput schema / properties / person / description
      Previous value: -"Only promises owned by this person (exact name, case-insensitive)."New value: +"Only promises owned by this person: the exact name as list_people returns it, case-insensitive. Omit for everyone."
    • addedInput schema / properties / project
      Added value: +{
      +  "description": "Only promises from meetings filed under this project id, from list_projects.",
      +  "type": "string"
      +}
  3. First observedv1.0.21

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/closed-world, so the description's job is supplementary context — and it delivers: result ordering (newest first), the two-bucket shape of the response, exclusion of completed promises, and the truncation caveat implied by 'older promises past the limit are left out'. No contradiction with the read-only annotations.

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 plus one routing sentence, all front-loaded: what it returns, how it's shaped, then where to go instead. No filler and no repetition of annotation or schema content.

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?

With an output schema present, return values need not be described, and the description still conveys ordering and list structure. For a zero-required-parameter read tool with full schema coverage, nothing an agent needs to call it correctly is missing.

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 every parameter is already documented with defaults, formats and examples (e.g. person must be the exact name from list_people). The description restates the two-list structure but adds no parameter-level detail beyond the schema, which is the expected baseline.

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?

Specific verb+resource ('open promises from recorded meetings') with scope qualifiers: newest-first ordering, a two-list split ('mine' vs 'waiting_on_others'), and exclusion of finished items. An agent can distinguish it from list_decisions and get_person without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete trigger phrasings ('what do I owe', 'what is overdue', 'what is Anna still waiting on') and explicitly routes to alternatives: get_person for a single colleague's full picture and list_people for exact name spelling. When-to-use and when-to-use-something-else are both stated.

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