Skip to main content
Glama
CronusL-1141

AI Team OS

by CronusL-1141
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

model_config_get

Get model governance state: available models (auto-discovered from local CC transcripts — the models you actually used), the current default startup model ("model" key of the OS API's own Claude Code settings.json), and per-model workflow…

Instructions

Get model governance state: available models (auto-discovered from local CC transcripts — the models you actually used), the current default startup model ("model" key of the OS API's own Claude Code settings.json), and per-model workflow agent usage over the last N days (orchestration charter observability: how much fable vs opus the fleet burned).

Input Schema

NameRequiredDescriptionDefault
usage_daysNoAggregation window for usage stats (default 7, max 90)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.11.2
    • addedInput schema / properties / usage_days
      Added value: +{
+  "default": 7,
+  "description": "Aggregation window for usage stats (default 7, max 90)",
+  "type": "integer"
+}
  2. First observedv1.9.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does add useful provenance ('auto-discovered from local CC transcripts', 'model key of the OS API's own Claude Code settings.json') that goes beyond structured fields, but it never states explicitly that the operation is read-only or that it has no side effects, and gives no auth or rate-limit context.

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?

The main payload is front-loaded in one sentence that enumerates the returned state. It is somewhat overstuffed with parenthetical commentary ('orchestration charter observability', 'how much fable vs opus the fleet burned') that adds flavor rather than agent-relevant signal, but the sentence still earns most of its length.

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?

An output schema exists, so return values need not be spelled out. The description covers data provenance and the aggregation window, which is sufficient for a single-parameter read tool. The absence of any explicit read-only statement is the only real gap.

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%, including the default of 7 and max of 90 for usage_days, so the baseline is 3. The phrase 'over the last N days' in the description adds essentially nothing beyond what the parameter schema already documents.

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 opens with a specific verb and resource ('Get model governance state') and then enumerates the three things returned: available models, startup default, and per-model usage over N days. It is clear what the tool does, though it does not name the sibling it complements (model_config_set) to make the read/write split explicit.

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?

Usage is only implied: it describes the governance state returned, so an agent can infer it is an inspection tool. There is no explicit when-to-use, when-not-to-use, or pointer to model_config_set for mutations, which would be the natural alternative here.

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