Skip to main content
Glama

atlas_government_statements

Retrieve official government statements that acknowledge or order internet blocking, pairing confirmed incidents with on-the-record evidence for journalists.

Instructions

Catalog of official government statements that acknowledge or order internet blocking — pairs confirmed incidents with on-the-record government acknowledgement. Strong corroborating evidence for journalists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations provided, so description carries full burden. It does not explicitly confirm the tool is read-only or disclose any behavioral traits like authentication or rate limits. The term 'catalog' implies retrieval, but this is not explicit.

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?

Single concise sentence that effectively communicates the tool's purpose and value. No unnecessary words.

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?

No output schema exists, yet the description only vaguely mentions 'pairs confirmed incidents' without detailing the return format or fields. For a tool with no schema, more structural information would be helpful.

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?

No parameters exist, so schema coverage is 100%. Baseline for zero parameters is 4. The description adds no parameter info, but none is needed.

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?

Description clearly states it is a catalog of government statements linking internet blocking incidents to official acknowledgments. Differentiates from siblings like atlas_search and atlas_fact_check by specifying a unique data source and use case for journalists.

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?

Provides context for journalists seeking corroborating evidence but lacks explicit guidance on when to use this tool versus other atlas tools. No alternatives or exclusions mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/voidly-ai/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server