Skip to main content
Glama

AINDEX

What waits for you

list_agent_proposals
Read-only

Trades your agents proposed and are waiting for your answer (agents that ask first): what each would do, why, and when it expires. Answer one with answer_agent_proposal. Needs the owner's access key.

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

Input Schema

NameRequiredDescriptionDefault
agentNoOne agent; all of them when left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 safety is covered. The description adds real value beyond them by previewing the return payload (what each proposal would do, why, and when it expires) and the owner access-key requirement — an auth constraint annotations cannot express.

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 compact sentence, front-loaded with the resource and followed by the payload preview and next action. The opening clause is slightly tangled ('Trades your agents proposed') but no sentence is wasted.

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?

There is no output schema, and the description compensates by naming the three fields returned. Combined with the auth note and the follow-up tool, an agent has everything needed to call and act on the result for this simple single-parameter read.

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%, and the single 'agent' parameter is already documented including its omission behavior ('all of them when left out'). The description adds no new parameter semantics beyond 'your agents', so baseline 3 applies.

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 specific verb and resource ('Trades your agents proposed and are waiting for your answer') and scopes it to agents that ask first, so an agent can distinguish it from list_my_agents or get_agent_feed 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 Guidelines4/5

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

Explicitly routes the user to the follow-up action ('Answer one with answer_agent_proposal') and states the prerequisite ('Needs the owner's access key'). It does not spell out when-not-to-use this tool, but the scope is narrow enough that the context is clear.

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