Skip to main content
Glama

Compute one engine fact for a chart

run_engine
Read-onlyIdempotent

Reviewer/developer tool. Computes one fact of one engine (see list_engines) for a deterministic chart, as of asOfDate for period and transit facts. Returns null in value when the chart cannot answer it.

Input Schema

NameRequiredDescriptionDefault
argsNoArguments matching the fact's schema in list_engines
dateYes
factYesFact name within the engine
nameNo
timeYes
placeNoCatalogue query or display label when explicit coordinates are supplied
engineYesEngine id from list_engines, for example natal, dasha, kp
asOfDateNo
latitudeNo
timezoneNoRequired IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata
longitudeNo
timezoneOffsetNoOptional fallback offset; derived from timezone and the requested local date when omitted

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context beyond that: it states that asOfDate applies to period and transit facts, and that the tool returns null in value when the chart cannot answer the requested fact.

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?

The description is two tight sentences with the purpose front-loaded. Each sentence contributes: the first establishes scope and prerequisite, and the second adds temporal semantics and null-return behavior.

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 complex 12-parameter tool with an output schema, the description covers the core purpose, prerequisite discovery tool, temporal scoping, and a key return-case behavior. It omits detailed parameter semantics, but the schema and output schema carry much of that burden.

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?

With 12 parameters and only 50% schema description coverage, the description does little to compensate. It clarifies the role of asOfDate for period and transit facts and points to list_engines for engine/fact selection, but it leaves critical required parameters like date and time unexplained, along with the place-versus-coordinates alternative.

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 gives a specific verb and resource: 'Computes one fact of one engine' for a deterministic chart, and points to list_engines for discovery. It is clear what the tool does, though it does not explicitly differentiate itself from the many analyze_* siblings beyond the 'Reviewer/developer tool' framing.

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?

'Reviewer/developer tool' implies an advanced or diagnostic use case, and 'see list_engines' gives the prerequisite for obtaining engine and fact names. However, it does not explicitly say when to use this instead of higher-level analysis tools or when not to use it.

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