Skip to main content
Glama
Sign In
asterism-mcp

asterism-mcp

by Plaetorius
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_works

Read-onlyIdempotent

Search titles and abstracts of all catalogued works, including paywalled papers, to answer what exists on a topic and filter results by publication year.

Instructions

Search titles and abstracts of every catalogued work (all years, incl. paywalled papers).

Use this for "what exists" questions; use `search` for full-text passages (open papers only).

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_works"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
offsetNo
year_toNo
year_fromNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description's job is to add coverage semantics — and it does, disclosing that only titles and abstracts are searched and that paywalled works are included. It omits pagination/result-cap behavior, which matters given limit/offset parameters.

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 the capability then the routing rule. No filler, no repetition of the tool name, and the sibling comparison follows the scope statement in the right order.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the selection guidance is complete. The gap is the four optional filtering/paging parameters left entirely undocumented for a tool with 0% schema coverage, leaving an agent to guess at year-range and pagination semantics.

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

Parameters2/5

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

Schema description coverage is 0% across 5 parameters, so the description must carry parameter meaning and largely does not. Only `query` gains implied semantics (it matches titles and abstracts); year_from, year_to, limit, and offset are never mentioned or explained.

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?

States a specific verb and resource ('Search titles and abstracts of every catalogued work') and adds scope qualifiers ('all years, incl. paywalled papers'). This is clearly separable from the sibling `search`, which the description itself contrasts against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: use this for 'what exists' questions, use `search` for full-text passages on open papers only. Both the when-to-use and the alternative are named with the discriminating condition (catalogued metadata vs. full text, paywalled vs. open).

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

Deploy Server

Other Tools