Skip to main content
Glama

Distribute Software

Send a story tip

submit_tip

Send the editors a story the site is missing. Needs an API key in the Authorization header (Bearer ); request one at https://distribute.software/submit. Tips go to a review queue and are never published automatically.

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": {
      "url": "<url>",
      "note": "<note>",
      "context": "<context>"
    },
    "name": "submit_tip"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe story's full http(s) link.
noteYesWhat the story is and why it matters.
contextYesA few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other personal details.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations only say it is a non-destructive, non-idempotent, non-open-world write, so the description adds real value: the Bearer API key requirement, a URL for obtaining a key, and the critical fact that tips go to a review queue and are never published automatically. It doesn't cover duplicate-submission behavior, rate limits, or failure modes, which keeps it short of a 5.

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?

Three tight sentences, front-loaded with the purpose, then the hard requirement (auth), then the outcome (review queue, not published). No padding.

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 write tool with no output schema, the description covers the essentials an agent needs to call it correctly: the auth requirement, where to get a key, and what happens to the submission. What happens on rejection, or whether a confirmation or ID comes back, is left implicit, so it is strong but not exhaustive.

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 every parameter, including context and llm_model analytics fields, is documented in the schema, so the baseline of 3 applies. The description adds nothing about parameter meaning, but it doesn't need to here.

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

Purpose5/5

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

A specific verb plus resource: 'Send the editors a story the site is missing.' It tells the agent this is a submission of a story tip and implies the resource is a story the site lacks, which separates it from the read-oriented siblings (get_story, search_stories, get_releases).

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 'a story the site is missing' implies when to use it, namely when the site doesn't already cover a story, and the review-queue note implies it isn't a publishing action. But there is no explicit when-to-use or when-not guidance, no mention of checking search_stories first to avoid duplicates, and no alternatives named.

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