Skip to main content
Glama

The Cultural Signal

Latest art-world news

latest_stories
Read-only

The latest art-world stories from The Cultural Signal's wire: auction results, exhibitions, acquisitions, appointments, fairs. Each story has the facts paragraph, an editorial signal, source institution, original press-release URL, event date and cities. Newest first, at most 2 per source.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
regionNoOnly stories with a city in this region.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value beyond that: result ordering ('newest first') and a deduplication rule ('at most 2 per source') that materially affects what the agent gets back and cannot be inferred from annotations or schema. It stops short of noting pagination or rate limits, which is acceptable for a read-only wire feed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with no filler; the wire/source identification and category list come first, followed by the payload description and ordering rule. Slightly list-heavy in the second sentence but every clause carries information an agent can use.

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 usefully enumerates returned fields (facts paragraph, editorial signal, source institution, press-release URL, event date, cities), which is exactly what an agent needs to judge relevance. For a trivial parameterless read feed this is nearly complete; the only gap is how 'limit' interacts with the per-source cap.

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 50%: 'region' is documented in the schema itself, and 'limit' is self-documenting via default=10, minimum=1, maximum=15. The description adds no syntax or format detail for either parameter, and the '2 per source' cap is not tied to how 'limit' counts results, leaving an ambiguity the agent must guess at.

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?

States a specific verb+resource ('the latest art-world stories from The Cultural Signal's wire') and enumerates the covered categories (auction results, exhibitions, acquisitions, appointments, fairs). An agent can tell this apart from search_stories because the scope is inherently recency-based rather than query-based, though the distinction is implied by 'latest' rather than stated.

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?

Usage is implied by 'latest' and 'newest first' — this is for pulling recent news, whereas search_stories would be for targeted lookups — but the description never says when to prefer one over the other or notes any exclusions. The ordering and per-source cap are behavioral facts, not selection guidance.

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