Skip to main content
Glama

The Cultural Signal

Search recent art-world coverage

search_stories
Read-only

Whole-word search over the most recent 200 stories (headline, body and tags). Use for an artist, gallery, museum, auction house, fair or city, e.g. 'Basquiat', 'Phillips', 'Art Basel'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_stories"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 the safety profile is covered. The description adds genuinely useful behavior beyond that: the corpus is capped at the 200 most recent stories and matching is whole-word across headline, body and tags, which tells the agent results are recency-bounded and literal.

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, zero filler, with the corpus scope and matching mode front-loaded before the usage examples. Every clause carries information an agent needs.

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?

For a two-parameter read-only search with no output schema, the definition covers scope, matching semantics and query intent well. The remaining gap is the unexplained 'limit' parameter and no hint about result shape, which is minor for a tool this simple.

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 description coverage is 0%, so the description must carry parameter meaning. It does explain what 'query' matches against (headline, body, tags) and gives example values, but the 'limit' parameter (default 8, max 20) is never mentioned, leaving half the parameters undocumented.

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 and resource ('Whole-word search over the most recent 200 stories') plus the fields searched (headline, body, tags), which is far more than a restatement of the name. It implicitly separates itself from a plain 'latest_stories' listing by being a query-driven search, but never names a sibling explicitly.

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?

Gives concrete when-to-use guidance with entity types (artist, gallery, museum, auction house, fair, city) and worked examples ('Basquiat', 'Phillips', 'Art Basel'). It stops short of stating when NOT to use it or which sibling to pick for browsing instead.

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