Skip to main content
Glama

silex_encyclopedia_lookup

Read-onlyIdempotent

THE SILEX 13-BRANCH LIVING ENCYCLOPEDIA: Search extreme-depth reference treatises and autonomous 15-minute peer-reviewed Current Happenings across all 13 branches and 48 sub-disciplines (Physics, Astronomy, Chemistry, Earth Science, Biology, Zoology, Botany, Virology, Medicine, Engineering, Computing, Math, History, Geography, Law/Economics/Psychology, Philosophy/Religion, Arts, Linguistics, Everyday Life, Biographies). [Pricing: Free discovery metadata; full HTTP 402 payload unlock from $0.003 USD in Nano ($XNO) via txHash, silexPass, or receiptToken.]

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": {
      "q": "<q>"
    },
    "name": "silex_encyclopedia_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesTopic or keyword search query (e.g. black holes, CRISPR, pharmacology, Roman Empire, syntax).
subNoOptional sub-discipline slug filter (e.g. astronomy-space, microbiology-virology, computing-information-technology).
branchNoAcademic branch slug filter (e.g. natural-physical-sciences, engineering-computing, history-archaeology; pass 'all' to search all branches).
txHashNoOptional 64-hex Nano ($XNO) mainnet send block hash for paid HTTP 402 payload unlock.
silexPassNoOptional Silex 0ms Prepaid Bearer Pass token (spass_...).
receiptTokenNoOptional 24h X-Silex-Receipt idempotent recovery token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / branch / description
      Previous value: -"Optional branch slug"New value: +"Academic branch slug filter (e.g. natural-physical-sciences, engineering-computing, history-archaeology; pass 'all' to search all branches)."
    • changedInput schema / properties / q / description
      Previous value: -"Topic or keyword search (e.g. black holes, CRISPR, pharmacology, Roman Empire, syntax)"New value: +"Topic or keyword search query (e.g. black holes, CRISPR, pharmacology, Roman Empire, syntax)."
    • changedInput schema / properties / sub / description
      Previous value: -"Optional sub-discipline slug (e.g. astronomy-space, microbiology-virology, computing-information-technology)"New value: +"Optional sub-discipline slug filter (e.g. astronomy-space, microbiology-virology, computing-information-technology)."
    • changedInput schema / required
      Previous value: -[
      -  "branch"
      -]New value: +[
      +  "q"
      +]
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, non-open-world), yet the description still adds material context: free discovery metadata versus an HTTP 402 paid payload unlock starting at $0.003 USD in Nano via txHash, silexPass, or receiptToken, plus a 15-minute refresh cadence for Current Happenings. That pricing/paywall behavior is exactly the kind of thing an agent cannot infer from the annotations, though it omits result limits, pagination, and what 'discovery metadata' actually returns.

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

Conciseness2/5

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

The front-loading is fine and the pricing note is genuinely useful, but roughly half the text is a sprawling parenthetical enumeration of ~21 disciplines introduced as '13 branches and 48 sub-disciplines' — internally inconsistent and irrelevant to selecting or invoking the tool. Marketing capitalization ('THE ... LIVING ENCYCLOPEDIA') further pads a description that could be two sentences.

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?

Given six parameters and no output schema, the description does explain the paid-unlock paths and freshness of the corpus, which is adequate for a search entry point. It leaves gaps an agent would want: whether results are paginated or capped, what the free 'discovery metadata' contains versus the unlocked payload, and how branch/sub filters interact with a query.

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 100%, so all six parameters (q, sub, branch, txHash, silexPass, receiptToken) are already documented in the schema with examples and patterns. The description only reinforces the payment parameters collectively via the pricing note and adds no syntax, format, or interaction detail beyond the schema, so the baseline of 3 applies.

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 uses a specific verb ('Search') applied to a named resource ('extreme-depth reference treatises' plus 'peer-reviewed Current Happenings'), so an agent can tell it retrieves encyclopedia/reference content rather than asking a question or fetching a news wire. It never names a sibling (e.g. silex_ask_instant, silex_hyper_search) to sharpen the boundary, and the marketing framing ('THE SILEX 13-BRANCH LIVING ENCYCLOPEDIA') plus the inflated discipline list muddies rather than clarifies scope.

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 only implied: the word 'Search' plus 'Topic or keyword search query' signals keyword lookup, and the branch/sub filters hint at narrowing. There is no explicit statement of when to choose this over silex_ask_instant, silex_hyper_search, or silex_breaking_news_wire, and no when-not-to-use case.

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.