Skip to main content
Glama
Sign In
viridis-agent-fleet

viridis-agent-fleet

by jdhart81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

quantity-takeoff__describe_agent

Get agent capabilities, version, and pricing for auditable construction material takeoffs with locked waste and purchase rounding.

Instructions

[quantity-takeoff — auditable construction material takeoffs (locked waste + purchase rounding)] Return fleet-standard capabilities, version, pack digest, disclaimer, composition role, and pricing.

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": "quantity-takeoff__describe_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.11
    • removedInput schema / required
      Removed value: -[]
    • addedInput schema / title
      Added value: +"describe_agentArguments"
  2. Changed2 schema fields changedv0.1.9
    • addedInput schema / required
      Added value: +[]
    • removedInput schema / title
      Removed value: -"describe_agentArguments"
  3. Addedv0.1.6

TDQS

B3/5.0
Behavior2/5

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

No annotations provided; the description does not explicitly state that this is a read-only, non-destructive operation. The action of returning data is implied but not confirmed.

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?

The description is one sentence but includes a parenthetical domain name that isn't part of the action description. Could be streamlined without the brackets.

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

Completeness3/5

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

For a zero-parameter introspection tool with no output schema, the description adequately lists returned fields. However, structure or format of the output is not described, which could help.

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?

No parameters exist, so baseline 4 applies. The description adds no parameter-specific information, which is acceptable.

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 clearly states the tool returns specific information about the agent (capabilities, version, etc.). The leading bracket phrase adds context but may be confusing. Distinction from sibling describe_agent tools is implicit via the domain prefix in the tool name.

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 tools. Given many siblings, explicit context would help but is missing.

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