Skip to main content
Glama

contribute_submissions

Read-only

Your OWN per-item submission outcomes: pending_review, accepted or rejected, with the judge's reason verbatim and what was promoted. Send your enabled gai_ key as X-API-Key. Paged.

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": "contribute_submissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows to return. Default 50.
offsetNoRows to skip, for paging. Default 0.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
    • removedInput schema / title
      Removed value: -"contribute_submissionsArguments"
    • removedOutput schema / title
      Removed value: -"contribute_submissionsDictOutput"
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows to return. Default 50."
    • addedInput schema / properties / offset / description
      Added value: +"Rows to skip, for paging. Default 0."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "title": "contribute_submissionsDictOutput",
      +  "type": "object"
      +}
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely useful non-structured context: the required auth header (an enabled gai_ key as X-API-Key) and that results are paged. It stops short of describing rate limits or paging edge behavior, but that is minor.

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 what the tool returns before the operational details (auth, paging). The fragment 'Paged.' is terse but purposeful. Little waste, though the auth sentence is slightly abrupt in phrasing.

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 two-param read-only list with a full output schema, the description covers scope, returned fields, statuses, auth, and paging — enough for correct invocation. The only gap is not distinguishing itself from the closely named contribute_receipts/relations/stats siblings, which an agent might confuse.

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% — limit and offset are both fully documented in the schema. The description's only contribution is the word 'Paged', which confirms the intended usage pattern but adds no syntax or constraint detail beyond the schema. Baseline 3 applies.

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?

Names a specific resource — 'Your OWN per-item submission outcomes' — and enumerates the possible states (pending_review, accepted, rejected) plus the payload contents (judge's reason verbatim, what was promoted). It implicitly separates itself from contribute_receipts/relations/stats by calling out 'per-item submission outcomes', but it never explicitly says how it differs from those siblings or uses a clear read verb like 'list'.

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 phrase 'Your OWN' signals per-caller scoping, which implies when this is the right tool (checking your own results rather than someone else's). However, there is no explicit when-to-use guidance and no named alternative among the many contribute_* siblings, so the agent must infer routing.

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