Read the currently displayed settled public Spotlight, including labeled house advertisements. Does not bid or pay.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds a meaningful behavioral guarantee: 'Does not bid or pay.' This clarifies there are no financial side effects, which is valuable context beyond the generic read-only annotation. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with no wasted words. The main action is front-loaded, and the key non-side-effect behavior is stated directly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With zero parameters, an output schema present, and annotations covering safety, the description is sufficient. It tells the agent exactly what is being read and explicitly rules out bidding/paying, so nothing essential is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and schema coverage is 100%, so there is no parameter detail for the description to add. Per the baseline for zero-parameter tools, this is strong enough.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly uses the verb 'Read' with a specific resource: the currently displayed settled public Spotlight, and explicitly notes it includes labeled house advertisements. This distinguishes it from sibling tools like get_spotlight and list_spotlights by emphasizing 'currently displayed' and 'settled.'
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description conveys when to use this tool: when the agent needs the currently displayed settled public Spotlight. It does not explicitly mention alternatives or exclusions, but the 'currently displayed' phrasing sets it apart from general get_spotlight or list_spotlights, giving clear contextual guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct purpose: retrieving the current spotlight, retrieving a spotlight by date, listing all spotlights, and reading documentation. There is no meaningful overlap or ambiguity between them.
All tool names consistently follow the verb_noun pattern (get_current_spotlight, get_spotlight, list_spotlights, read_agent_docs). Naming style is uniform and predictable.
Four tools is appropriately scoped for a read-only spotlight browsing server. Each tool covers a necessary operation without unnecessary bloat or missing essentials.
The toolset covers the core lifecycle of reading public spotlights: current, by date, and a browsable list, plus documentation. A search or filter capability could be a minor enhancement, but there are no critical gaps for the stated purpose.