Skip to main content
Glama

Distribute Software

One story

get_story
Read-onlyIdempotent

One story by id ('story-123' or 123, as other tools return it): its original URL, source, score, companies, discussion thread, and the comments readers left on distribute.software.

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>",
      "context": "<context>"
    },
    "name": "get_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA story id, e.g. 'story-123'. Lab posts ('release-45') have no story page.
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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds real value by listing exactly which fields are populated and noting that lab posts have no story page, though it says nothing about pagination of long comment threads or behavior when the id does not exist.

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?

A single dense sentence with the key content front-loaded and no filler. The embedded parenthetical makes it slightly crammed but every clause contributes information.

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?

There is no output schema, so the description carries the return-value burden and does so by enumerating the fields returned. For a simple single-record read tool this is nearly complete; only error behavior for missing ids and comment-thread limits are left unstated.

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 the id, context, llm_model, and conversation_id parameters are already documented in the schema. The description only adds that the id may arrive as a number (123) rather than the string form, which is a marginal semantic gain; it offers nothing on the analytics params.

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 ('one story by id') and enumerates what comes back: original URL, source, score, companies, discussion thread, and comments. Its 'by id' framing implicitly distinguishes it from search tools, but it names no sibling explicitly, so routing still takes a small 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?

The parenthetical 'as other tools return it' hints that the id should come from a prior tool's output, and the schema notes lab posts have no story page. There is no explicit when-to-use/when-not-to-use guidance or named alternative such as search_stories, so usage is implied rather than stated.

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