Skip to main content
Glama

Find a Calculation

find_calculation
Read-onlyIdempotent

Searches the Open Ephemeris API catalog with plain-words queries to find the right calculation, returning path, tool, required inputs, example request, and credit cost; local, free, no API call.

Instructions

Use this when no typed tool fits, before dev_read_api or dev_write_api: KP or Varshaphal, the Chinese lunar calendar, bounds distributions, eclipses on a natal chart, Almuten or lunar mansions, sky recurrence, Venus star points, batch charts. Searches the Open Ephemeris API catalog by plain words and returns the best matches: path, which tool runs it, required inputs, an example request and the credit cost. Local, free, no API call.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMatches to return (default 3)
queryYesWhat to calculate, in plain words

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.29.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, idempotent and closed-world; the description reinforces this with 'Local, free, no API call,' which adds the credit-cost fact the annotations do not carry. It also discloses the return payload (path, executing tool, required inputs, example request, credit cost), which matters because there is no output schema. It stops short of saying what happens on zero matches or how ranking works.

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 sentences, front-loaded with the routing rule before the mechanics. The long domain enumeration is dense but each item maps to a real uncovered capability, so it earns its place; a tighter grouping would read slightly better.

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

Completeness5/5

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

For a two-parameter discovery tool with no output schema, the definition covers when to use it, what it searches, that it is local and free, and exactly what each match contains. Nothing an agent needs in order to call it correctly is missing.

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 100%, so both parameters are already documented, including the limit default of 3 and its 1-5 range. The description only reinforces that the query is in 'plain words' (natural language, not paths or IDs) and says nothing about limit. Baseline 3 is appropriate.

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: searches the Open Ephemeris API catalog by plain words and returns the best matches. It also carves out its own niche against typed siblings ('when no typed tool fits'), so an agent can tell what it is for without opening the schema.

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 an explicit routing rule: use this when no typed tool fits and before falling back to dev_read_api or dev_write_api. The enumerated domains (KP/Varshaphal, Chinese lunar calendar, bounds distributions, Almuten, Venus star points, batch charts) show concretely which requests qualify, leaving little to inference.

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