Skip to main content
Glama

Rosmaryn

Search the Rosmaryn encyclopedia

search_encyclopedia
Read-only

Find pages of the Rosmaryn encyclopedia (Human Design, astrology, numerology, mirror hours) and return their titles, types and links. Use it to cite a reference page on rosmaryn.app.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWords to look for, e.g. "gate 34", "Mars in Leo", "life path 7".
languageNoLanguage of the results (default en).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with that by framing the tool as reading a fixed internal corpus. It adds the return fields (titles, types, links), which is useful since there is no output schema, but says nothing about matching behavior (keyword vs fuzzy), ranking, no-result handling, or rate limits.

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: what it finds and returns first, the intended use case second. Nothing redundant and nothing buried.

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 three-parameter read-only search with no output schema, the description covers the corpus, the domains, the returned fields, and the citation use case. Only edge behavior — empty results, ranking, and the meaning of limit — is left unstated, which is a minor gap rather than a blocking one.

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 67%, and the schema itself already supplies query examples and the language enum with its default. The description adds no meaning to query syntax, to what limit actually controls (result cap), or to how language interacts with results, so it does not compensate for the undocumented limit parameter.

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 names a specific verb and resource — 'Find pages of the Rosmaryn encyclopedia' — and even scopes the corpus domains (Human Design, astrology, numerology, mirror hours) plus the returned fields. It does not explicitly contrast with list_calculators or upcoming_sky_events, but the encyclopedia resource is self-evidently distinct from calculators and sky-event listings.

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?

'Use it to cite a reference page on rosmaryn.app' gives a concrete usage context, so an agent knows this is the citation-lookup path rather than a general search. There are no stated exclusions or when-not conditions, and no explicit routing to the sibling tools.

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