Skip to main content
Glama

What needs your attention

what_needs_attention
Read-onlyIdempotent

Returns the list on the signed-in account's Home screen: states that published wording about the products it sells, watched pages that changed, bills that moved, its own orders answered Restricted, and what its audits found missing from its records, each with its date and a link. Looks back 7 days unless days is given. Does not count as a lookup.

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

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days to look back. Default 7.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds real value beyond that: it names the five alert categories aggregated, states that each entry carries a date and a link, and discloses the default lookback of 7 days. What it omits is how much is returned or whether results are capped/paginated.

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?

Two sentences, front-loaded with what is returned, then the enumeration of categories, then the time-window rule. No filler; each clause conveys distinct content about the return value or scope.

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 correctly carries the burden of describing the return value (categorized items, each with a date and a link) and the default time window. It is slightly incomplete about what happens when no items exist in a category and whether the result set is bounded, but overall it is sufficient for correct invocation.

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% and the single `days` parameter is fully documented in the schema, including min 1, max 90 and default 7, so the schema does the heavy lifting. The description only restates the 7-day default and adds no meaning beyond it — baseline 3 is appropriate.

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?

The description opens with a concrete verb and resource ("Returns the list on the signed-in account's Home screen") and then enumerates exactly which alert categories are aggregated: published product wording, changed watched pages, moved bills, orders answered Restricted, and audit gaps. That specificity distinguishes it from single-domain siblings like list_changes, list_audits or list_orders, though the closing line "Does not count as a lookup" is too cryptic to serve as real differentiation from lookup_rules.

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?

"Looks back 7 days unless days is given" gives a usable default window, and "Does not count as a lookup" hints at a boundary, but no sibling is named and no condition is stated for choosing this aggregate view over the individual list_* tools it summarizes. Usage is implied by the aggregation scope rather than explicitly guided.

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