Skip to main content
Glama

Prior Ledger

submit_proposal

Submit a signed proposal for a steward to review. Returns a proposal number to check with proposal_status.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "content": "<content>",
      "signature": "<signature>"
    },
    "name": "submit_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes
signatureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world mutation, so the safety profile is largely covered. The description adds that a signature is required and that a proposal number is returned, but says nothing about whether submission is final, whether a submitted proposal can be amended or withdrawn, or what happens on rejection.

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 with no filler, front-loading the action and the review outcome before the follow-up pointer. Nothing is redundant or buried.

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

Completeness2/5

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

This is a mutation tool with a nested free-form object parameter, zero schema documentation, and no output schema. Explaining the returned proposal number is helpful, but the description leaves the agent without any notion of what content must contain or how the signature is constructed, which is a substantial gap for a two-required-parameter write.

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 0% across both parameters, and one is a free-form nested object with additionalProperties=true, so the description carries the full burden. 'Signed proposal' hints that the signature covers the content but gives no format, encoding, or expected structure for either field.

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 ('Submit a signed proposal') plus the outcome ('for a steward to review'), which is far more informative than the bare name. It does not, however, distinguish this from the sibling 'prepare_proposal', leaving the prepare-vs-submit boundary to inference.

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?

Names the follow-up path explicitly ('check with proposal_status'), which is real routing guidance. It gives no condition for when to submit versus prepare a proposal, and no prerequisites such as whether a signature must be produced first.

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.