Skip to main content
Glama
Sign In
ASTRA

ASTRA

by christophejlegros-lgtm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

tcai_development

Read-onlyIdempotent

Track longitudinal development across nascent, reactive, integrative, and reflective stages, using composite-proxy level, stability and meta-representation for second-order self-monitoring over time.

Instructions

Longitudinal developmental tracking (DevelopmentTracker port): coarse stage (nascent→reactive→integrative→reflective) from the running composite-proxy level, stability and meta-representation score. Second-order self-monitoring over time.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description contributes the output semantics (stage, stability, meta-representation score) but adds nothing about auth, rate limits, freshness, or what the running composite-proxy depends on, which is limited value beyond the structured fields.

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?

Roughly three sentences, front-loaded with the core purpose and then the output detail. No filler, though parenthetical jargon ('DevelopmentTracker port', 'composite-proxy level') costs a little clarity for a short description.

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 parameterless, read-only tool with annotations covering safety and no output schema, the description supplies the return semantics (stage names, stability, meta-representation score). It is close to complete; only sibling differentiation and prerequisites are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and there is no parameter syntax the description needs to compensate for. Nothing is missing on this dimension.

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?

States a specific verb+resource ('Longitudinal developmental tracking') and even enumerates the output dimension (stage nascent→reactive→integrative→reflective plus stability and meta-representation score). However it does not distinguish itself from close siblings like tcai_second_order or tcai_self_model, and the phrase 'Second-order self-monitoring over time' actively muddies the boundary with tcai_second_order.

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 condition that selects this tool over the many tcai_* siblings, and no exclusion statements. The agent is left to infer usage entirely from the terse purpose.

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