Skip to main content
Glama
Sign In
ASTRA

ASTRA

by christophejlegros-lgtm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

fcs_taxonomy

Read-onlyIdempotent

Filter and retrieve 13 molecular classes as 17 species-function pairs by causal role, Pareto stratum, or pair ID to compare function roles, distance, time constants, and epistemic status.

Instructions

The thirteen molecular classes as seventeen species–function pairs: causal role, distance to the carrier d, time-constant range τ, ablation degree, Pareto stratum and declared epistemic status. The ordering is of FUNCTIONS, not of substances: one species may occupy two distant places.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fcs_taxonomy"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoFilter to one causal role.
pairIdNoA single pair by its v1.1 class identifier, e.g. "2a", "10b".
stratumNoFilter to one Pareto stratum.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds domain context (that ordering is of functions, not substances, and a species may appear twice), which helps interpret results, but it says nothing about whether filters combine, defaults, or the shape of the return.

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

Conciseness3/5

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

Two sentences with no obvious padding, and the field list is front-loaded. However, the first sentence is a dense wall of unglossed jargon (distance to carrier d, time-constant range τ, ablation degree) that costs more reading effort than it earns.

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?

This is a read-only, no-output-schema lookup whose safety profile is fully carried by annotations, so the description needn't explain return values. It supplies the key conceptual caveat about function-ordering, which is genuinely useful, though it omits how the three filters behave together.

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 the schema fully documents role, pairId, and stratum. The description echoes two of these (causal role, Pareto stratum) but adds no syntax or semantics beyond the schema, leaving the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys that this exposes an FCS species–function taxonomy (thirteen classes as seventeen pairs, with fields like causal role and Pareto stratum), but it uses no clear action verb and never says whether the tool lists the whole taxonomy, queries it, or returns one pair. It also does not differentiate itself from closely-named siblings such as fcs_levels, fcs_stratify, or fcs_report.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of the filtering options, and no alternative or exclusion named. An agent has to infer that this is the taxonomy lookup versus fcs_levels or fcs_stratify purely from the name.

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