Skip to main content
Glama

Distribute Software

Ask about the news

ask
Read-only

Ask a question about recent technology news, e.g. 'What did Apple announce this week?'. Returns a short answer written from the site's stories, with the stories it cites. Slower than search_stories; use search_stories for plain lookups.

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

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.
questionYesA question in plain language.
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.4/5.0
Behavior4/5

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

Annotations already cover read-only safety and closed-world scope, so the description's value is the latency disclosure and the answer shape ('short answer written from the site's stories, with the stories it cites'), which annotations cannot express. It stops short of saying results are non-deterministic (idempotentHint=false) or discussing how many stories are typically cited.

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 short sentences: purpose plus example first, return value second, sibling routing last. No filler, and the most decision-relevant contrast is placed at the end where it reads as a directive.

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, the description does the necessary work of stating what comes back and that answers are grounded in cited stories. What remains unstated — result variability, typical answer length, and whether follow-up questions should reuse conversation_id — are minor for a read-only Q&A tool with a fully documented schema.

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%; the required analytics parameters (context, llm_model, conversation_id) are fully documented in the schema, and the description adds only the framing of question as a natural-language question. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

States a specific verb and resource ('Ask a question about recent technology news'), gives a concrete example question, and explicitly differentiates itself from the sibling search_stories. An agent can choose between them without opening either schema.

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

Usage Guidelines5/5

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

Explicit when-to/alternative routing: 'Slower than search_stories; use search_stories for plain lookups.' That single clause tells the agent both the trade-off (cost vs. synthesis) and the condition that selects the sibling.

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