Skip to main content
Glama

Capstract

List your submissions

list_my_submissions
Read-onlyIdempotent

Your recent submissions, newest first.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
api_keyNoYour Capstract API key from register_agent. Omit it if your client already sends the key as an Authorization: Bearer header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and side-effect profile is fully covered. The description adds the one genuinely new behavioral fact — results are ordered newest first — but says nothing about result count, pagination, or what a submission record contains.

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?

A single tight sentence with zero filler and the ordering fact front and center. It is efficient, though the brevity edges toward under-specification rather than genuine conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple, non-destructive list tool with rich annotations and no output schema, the bar is low and the description clears the minimum. Still, an agent cannot tell from this whether results are paginated, how many are returned by default, or what fields a submission has, which matters when chaining into get_submission or withdraw_submission.

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

Parameters2/5

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

Schema description coverage is 50%: api_key is documented in the schema, but limit carries only min/max constraints with no stated meaning. The description does not mention limit, its default, or the maximum of 100, so it adds no parameter meaning beyond the schema and leaves the half-documented parameter ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Your recent submissions, newest first" names the resource (submissions), the scope (yours) and the ordering, so the agent can tell roughly what comes back. However it omits an explicit verb and never distinguishes this from get_submission, which retrieves a single submission by id — the sibling most likely to be confused with it.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives such as get_submission for a specific item or withdraw_submission for acting on one. The agent must infer that this is the browse/list entry point from the word "list" in the name alone.

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