Skip to main content
Glama

List saved context items

list_context
Read-only

List the saved context items the Phone Bud user can attach to a call (a payment card, an address, a membership number…). Returns each item's id, title and tags, never its contents. Pass ids to make_call or start_campaign as context_ids and the calling agent can use the details on the call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds meaningful behavior beyond them: it discloses the exact return shape (id, title, tags) and explicitly warns that contents are never returned, which prevents an agent from expecting sensitive data. It does not cover pagination or empty-list behavior.

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, front-loaded with the action and resource, followed by the viable next step. No filler or restatement of the title.

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 no output schema present, the description compensates by naming the returned fields (id, title, tags) and excluding contents. Combined with the annotations, an agent has everything needed to call it and to use the results correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero input parameters, so the baseline of 4 applies; the description correctly needs to explain no arguments. It adds no parameter confusion because none exist.

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 opens with a specific verb and resource ('List the saved context items') and immediately glosses the resource with concrete examples (payment card, address, membership number), so an agent knows exactly what domain object this returns. It is clearly distinct from the other list_* siblings in that it enumerates attachable data items rather than agents, campaigns or contacts.

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?

It gives explicit downstream usage: pass the returned ids to make_call or start_campaign as `context_ids` so the calling agent can use the details live on the call. That is strong when-to-use guidance, though it does not state exclusions or prerequisites (e.g. whether items are per-user or per-workspace).

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