kosmos.info.pl

NASA's Astronomy Picture of the Day

astronomy_picture

Read-onlyIdempotent

Today's Astronomy Picture of the Day from NASA: its title, explanation (machine-translated into Polish with lang pl, when the translation is ready), credit and image address. Only today's picture.

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": "astronomy_picture"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	Language of the answer: pl (default) or en

Output Schema

Name	Required	Description
`date`	Yes
`link`	Yes	The page on kosmos.info.pl
`image`	No
`notes`	No
`title`	Yes
`credit`	No
`media_type`	No
`explanation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotations already declare a safe, read-only, idempotent operation, and the description adds useful behavioral context: the explanation may be machine-translated into Polish when lang=pl and only when the translation is ready. It could be more explicit about what happens if the translation is not ready, but it adds meaningful context beyond the annotations.

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?

The description is compact and front-loaded: it names the source, lists the returned fields, notes the translation caveat, and closes with the scope limitation. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read-only tool with annotations and an output schema, the description supplies the necessary scope, return content, and language behavior. Nothing critical is missing for an agent to decide whether and how to call it.

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?

Schema coverage is 100%, so the enum values are already documented. The description adds useful meaning by explaining that lang=pl triggers a machine-translated Polish explanation and that the translation may not always be immediately available.

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?

The description states a specific resource and action: it returns today's NASA Astronomy Picture of the Day, including title, explanation, credit, and image address. The sentence 'Only today's picture' explicitly distinguishes the scope from archive or historical astronomy tools.

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

Usage Guidelines4/5

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

The description makes clear this is for today's picture only, which implicitly warns against using it for historical APOD lookup. It does not explicitly name sibling tools as alternatives, but the scoping sentence provides clear usage context.

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

All kosmos.info.pl tools Inspect

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

Need Help?