Skip to main content
Glama

propose_protocol

Submit a protocol proposal for review, validate it against base constraints, and calculate a risk score so it can be approved before becoming active.

Instructions

Submit a new protocol proposal for review. Validates against base constraints and calculates risk score. LLMs and users can submit proposals which must be approved before becoming active.

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": {
      "projectDir": "<projectDir>",
      "protocol": "<protocol>"
    },
    "name": "propose_protocol"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoTags for the proposal
sourceNoSource of the proposal (default: llm)
priorityNoReview priority (0-100, default: 50)
protocolYesThe protocol to propose
rationaleNoDesign rationale and decisions
projectDirYesAbsolute path to the project directory
descriptionNoWhy this protocol is needed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that the proposal is validated against base constraints, that a risk score is computed, and that the protocol is not activated until approved. It omits whether validation failures reject the submission or merely record the score, whether state is persisted immediately, and what permissions or limits apply.

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?

Three short sentences, front-loaded with the action, then validation behavior, then lifecycle. Minimal waste; the 'LLMs and users can submit proposals' clause is largely redundant with the first sentence.

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?

This is a complex tool with seven parameters, deep nested objects, and no output schema, so the description should explain what comes back. It mentions a computed risk score but never says the result is returned or what else is in the response, and it is silent on error behavior when base constraints are violated.

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%, so every one of the seven parameters is already documented in the schema, and the baseline is 3. The description adds only loose mapping ('base constraints' to constraints, 'risk score' presumably derived from priority/rationale) and no format or syntactic meaning beyond the schema.

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 new protocol proposal for review'. The lifecycle phrase 'must be approved before becoming active' positions it upstream of review/approval siblings without naming them. It is clear what the tool does, though no sibling is named explicitly.

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 description implies the workflow position (propose, then approve, then become active) and that both LLMs and users are legitimate callers, which is useful context. It gives no explicit when-not-to-use guidance or prerequisite conditions, and does not name approve_protocol or protocol_register as the next or alternative step.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.