Skip to main content
Glama

Mastering Financial Markets

Browse public user proposals

list_user_proposals
Read-onlyIdempotent

Read the separate public user-proposal history, including final outcomes. These assertions are separate from official audits; next_cursor identifies another results page.

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

Input Schema

NameRequiredDescriptionDefault
afterNoCursor returned with the previous page; omit it for the first page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / after / description
      Added value: +"Cursor returned with the previous page; omit it for the first page."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description usefully adds that results include final outcomes (completeness) and that a cursor yields another page (pagination), but it names that cursor 'next_cursor' while the schema field is 'after', which muddies rather than clarifies the behavioral contract.

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?

Two short sentences with the scope stated first and the provenance caveat second; nothing is padded. The final clause is slightly wasteful because it restates pagination with a cursor name not used in the schema.

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 simple read-only, single-cursor listing tool with no output schema, the description covers what is returned (proposals with final outcomes), the data's non-authoritative nature, and pagination. Only the cursor-name mismatch and the lack of any sibling routing keep it from being complete.

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 'after' parameter is fully documented, so the baseline is 3. The description's only parameter-adjacent content is the pagination remark, which introduces a differently named cursor ('next_cursor') rather than adding meaning to 'after'.

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 ('Read the separate public user-proposal history, including final outcomes') and clarifies the data is distinct from official audits. An agent can tell what it retrieves, though 'separate' is left dangling without saying separate from which specific sibling or system.

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?

The sentence 'These assertions are separate from official audits' implies this is the place to look for unofficial user-asserted proposals rather than audit data. However, it gives no explicit when-to-use versus siblings like search, list_datasets, or request_update, and no prerequisites.

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