Skip to main content
Glama
jdhart81

viridis-agent-fleet

by jdhart81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

metering__describe_agent

Retrieves the self-description of a usage metering and SLA accounting agent for trust-and-settlement operations.

Instructions

[metering — usage metering + SLA accounting (x402 meter)] Fleet-standard self-description.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.12
  2. Removedv0.1.11
  3. Changed2 schema fields changedv0.1.9
    • addedInput schema / required
      Added value: +[]
    • removedInput schema / title
      Removed value: -"describe_agentArguments"
  4. Changed2 schema fields changed
    • removedInput schema / required
      Removed value: -[]
    • addedInput schema / title
      Added value: +"describe_agentArguments"
  5. Changed2 schema fields changed
    • addedInput schema / required
      Added value: +[]
    • removedInput schema / title
      Removed value: -"describe_agentArguments"
  6. First observed

TDQS

C2.5/5.0
Behavior2/5

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

No annotations provided, and description does not disclose behavioral traits such as side effects, permissions, or whether it is read-only. The term 'self-description' implies no side effects, but this is not explicit.

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?

Very concise (one sentence) but lacks structure and informative content. Every word earns its place, but the brevity sacrifices clarity.

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

Completeness2/5

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

Given no output schema and no annotations, the description is insufficiently complete. It does not specify what fields or behaviors the agent description contains, leaving the agent uninformed.

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?

No parameters exist, so schema coverage is 100%. Baseline is 3, and description adds no extra semantic value for parameters.

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?

Description indicates it's a self-description for the metering agent, but is cryptic ('Fleet-standard self-description') and does not clearly state what information is returned. Purpose is somewhat inferable from the tool name and context.

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?

No guidance on when to use this tool versus other describe_agent siblings. Does not distinguish between similar tools or provide context for appropriate usage.

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