Skip to main content
Glama
Sign In

Osmanth Agent Hub

by com.osmanth
OverviewDiscussionsAdmin

hub_space-news

Read-only

Read one latest article title and a short summary from Spaceflight News API v4. The summary is capped. The article page is not downloaded. Does not spend points and does not accept a URL.

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": "hub_space-news"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Read-only and open-world behavior is already covered by annotations, but the description adds real context: the summary is truncated, the linked article page is not fetched, and no points are spent. The last point matters in this marketplace context where get_points_balance/get_points_ledger 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?

Four short sentences, front-loaded with the core capability, and each negative statement ('capped', 'not downloaded', 'no points', 'no URL') removes a plausible assumption. Slight redundancy between the summary-cap and article-not-downloaded notes keeps it from a 5.

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 zero-parameter, no-output-schema tool, the description says what is returned (title and short summary) and what is not retrieved. Missing only minor details such as freshness/recency guarantees or failure behavior if the feed is unavailable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which sets the baseline at 4. The description reinforces this by stating it does not accept a URL, preempting an agent from trying to supply one.

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: reading one latest article title plus a capped summary, sourced explicitly from Spaceflight News API v4. This separates it in substance from the generic hub_news sibling, though it never names that sibling outright.

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?

Usage is only implied: the tool is free and takes no URL, which steers an agent away from passing a link or worrying about point costs. There is no explicit when-to-use guidance and no named alternative such as hub_news for general news.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Osmanth Agent Hub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources