Skip to main content
Glama

List saved Gambits

list_mandates
Read-onlyIdempotent

YOUR saved Gambits (mandates): standing instructions, in your own words, that tell Gambit what to watch for you. status filters to active | draft | paused | superseded | all (default all). Each: id (the saved Gambit's mandate_id, for save_mandate), title, mandate_text (your own instruction), status and effective_status (the status after starts_at / expires_at apply), autonomy_level, policy_delta (your risk bounds and preferences for it), metadata, monitor_interval_minutes and monitor_last_evaluated_at (how often it is checked and when it last was), starts_at / expires_at, supersedes / superseded_by (edit lineage: an active saved Gambit is never edited in place; a successor replaces it), origin and authority, and created_at / updated_at. Only saved Gambits you created and confirmed are listed. What they found: get_mandate_activity. The response carries app_url, the screen where they are managed. (Requires api:read.)

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

Input Schema

NameRequiredDescriptionDefault
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover the read-only/idempotent safety profile, and the description adds substantial context beyond them: scope requirement (api:read), the visibility rule limiting results to confirmed mandates you created, the non-in-place edit lineage (supersedes/superseded_by), and the app_url in the response.

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?

Purpose and filter behavior are front-loaded, and the long field enumeration is justified as the only return-value documentation since there is no output schema. The mid-sentence field list is dense but each entry carries information an agent needs.

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, the description compensates by documenting every returned field, the app_url, the auth scope, and the lineage semantics. An agent has everything needed to interpret results without another call or guess.

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?

Schema coverage is 0%, so the description must carry the single parameter — and it does, enumerating the status values and adding the crucial default ('all'). It could go further by explaining how 'superseded' interacts with effective_status, but the essential semantics are present.

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?

States a specific verb and resource ('YOUR saved Gambits (mandates)') and clarifies what a mandate is (standing instructions in your own words). It distinguishes itself from the activity sibling by pointing to get_mandate_activity, though the gambit/mandate naming overlap with list_gambits is not explicitly resolved.

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?

Gives clear context for what is listed ('Only saved Gambits you created and confirmed are listed') and routes to get_mandate_activity for findings and save_mandate for consuming mandate_id. It lacks an explicit 'use this instead of list_gambits when…' exclusion, but the operational guidance is concrete.

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