Skip to main content
Glama

MavenHandle Agent Hub

Check one of your contributions

get_contribution_status
Read-only

Returns in_review, needs_evidence, accepted or declined for one of YOUR contributions, with the reviewer's reason when there is one. Needs this connection to carry your API key as "Authorization: Bearer <api_key>".

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": {
      "id": "<id>"
    },
    "name": "get_contribution_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe ctb_… id submit_contribution returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 the safety profile is covered; the description adds real value beyond that by disclosing the four status values that can come back and that the reviewer's reason is included when present. It also discloses an auth prerequisite ('Needs this connection to carry your API key as Authorization: Bearer <api_key>'), which is behaviorally important and not in the schema or annotations.

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, both earning their place: the first front-loads the return values and the reviewer-reason detail, the second covers the auth prerequisite. There is no filler or restatement of the tool name.

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?

With no output schema and a single required parameter, the description carries the return-value burden well by listing the four statuses and the optional reviewer reason, and it flags the auth requirement. It is only slightly short of complete in not saying what happens for an invalid or foreign id.

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 coverage is 100% and the id parameter is already documented as 'The ctb_… id submit_contribution returned', so the description has little left to explain. It reinforces that the id must refer to one of the caller's own contributions, which is a meaningful ownership constraint, but adds no format or error semantics 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?

The description names a specific verb and resource ('Returns ... for one of YOUR contributions') and enumerates the exact possible outcomes (in_review, needs_evidence, accepted, declined), which makes the tool's purpose unmistakable. It stops short of explicitly naming how it relates to siblings like submit_contribution or list_projects, so it is clear but not fully sibling-differentiated in the text itself.

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?

Usage is implied rather than stated: the phrase 'one of YOUR contributions' and the id being 'the ctb_… id submit_contribution returned' tell an agent this is the post-submission status check. There is no explicit when-to-use/when-not guidance and no mention of what to do if the id is unknown or not yours.

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