Skip to main content
Glama

Distribute Software

Trending questions

trending_questions
Read-onlyIdempotent

Searches many readers of distribute.software made this week, most asked first: a quick read on what people want to know about the news.

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

Input Schema

NameRequiredDescriptionDefault
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

B3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds behavior beyond that: the data source (readers of distribute.software), the recency window ('this week'), and the sort order ('most asked first'), which are real selection-relevant traits. It does not disclose result volume, limits, or whether context strings are logged server-side beyond what the schema says.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no padding, and the source and ranking come early enough to be useful. However, the dropped noun and run-on phrasing force re-reading, so brevity is partly squandered on ambiguity rather than earned.

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?

For a three-parameter read tool with annotations and full schema coverage, the description is close to sufficient, but with no output schema it should say what a result is (a list of questions? with vote counts? how many?) and there is no indication of scope limits. The one sentence leaves the return shape and ranking signal under-described.

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 unusual analytics parameter (context), llm_model, and conversation_id are all fully explained in the schema. The description adds nothing about parameters, which is acceptable at this coverage level but is baseline rather than added value.

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

Purpose3/5

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

The sentence is grammatically broken ('Searches many readers of distribute.software made this week') but it can be parsed as searching questions asked by readers of distribute.software in the past week, ranked by frequency. That gives a verb+resource+scope, but the omission of the object noun leaves the agent to reconstruct the purpose. It also does not name or distinguish itself from plausible siblings such as search_stories, get_today, or ask.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'a quick read on what people want to know about the news' hints at a light-touch use case, but there is no explicit when-to-use instruction, no when-not, and no pointer to any of the nine siblings. An agent cannot tell from this text whether to call trending_questions before search_stories or get_today.

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