OpenWeather for agents

Account status

account_status

Read-onlyIdempotent

Reads the account behind the secret: tier, accepted Terms version, the products it may call, the one balance in credits (granted plus bought, minus spend), the last 30 days of usage per day, product and key, and the 50 latest balance movements. Pass the secret sign_up returned as the secret argument; the data key your client configuration sends cannot read the account and answers 403 wrong_credential. Charges nothing; without a string the platform answers 401 invalid_key.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`secret`	No	the account's secret — the string sign_up returned as secret; the client configuration's header holds the data key, which this tool cannot use; when both are present the argument wins

Output Schema

TableJSON Schema

Name	Required	Description	Default
`body`	No
`fault`	No
`usage`	No
`record`	No
`status`	No
`account`	No
`headers`	No
`upstream`	No
`body_text`	No
`configure`	No
`transport`	No
`key_source`	No
`request_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 6, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, it discloses that the call charges nothing, what happens when secret is omitted (401 invalid_key), and why the data key fails (403 wrong_credential). This gives an agent a realistic picture of behavior.

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 dense sentences with no filler; the output list is front-loaded, then required input, then failure modes. Every sentence carries operational value.

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 single-parameter read tool with a full output schema, the description covers what it returns, how to authenticate, failure modes, and cost. Nothing an agent needs to invoke it correctly is missing.

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

Parameters5/5

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

Even though the schema covers the secret parameter well, the description adds actionable meaning: the secret must be the one sign_up returned, the data-key header cannot be used, and omitting a string yields a specific 401. This is more than the schema alone provides.

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 names a specific verb and resource: 'Reads the account behind the secret' and enumerates the exact returned data (tier, accepted Terms version, products, balance, usage, movements). This clearly distinguishes it from siblings like list_products or fetch_data.

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?

It gives clear usage context: pass the secret returned by sign_up, not the data key from client configuration, and explicitly warns that the data key yields 403 wrong_credential. It does not name sibling alternatives, but the different purpose is obvious enough that no overlap confusion is likely.

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

All OpenWeather for agents tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool has a single unambiguous role: catalogue browsing, data fetching, account creation, account status, and top-up. Even get_product and list_products are cleanly separated by singular/plural and detail level.

Naming Consistency4/5

Most tools follow a verb_noun pattern (fetch_data, get_product, get_topup_link, list_products), and all names are lowercase snake_case. account_status and sign_up break the verb_noun pattern, but they are still readable and predictable.

Tool Count5/5

Six tools is a well-scoped set for an API platform server: discovery, data access, account monitoring, and top-up each have dedicated coverage. No tool feels redundant, and the count is appropriate for the server's purpose.

Completeness4/5

The set covers the full usage loop: sign up, discover products, fetch data, check balance/usage, and top up. Minor gaps exist — sign_up references a login_to_link action that no tool provides, and there is no key rotation or management — but they do not block the primary agent workflow.

Resources

Need Help?