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

viridis-agent-fleet

by jdhart81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

quantity-takeoff__list_material_pack

Retrieve material pack details including version, digest, coverage, shapes, rebar sizes, roof pitches, and unsupported policy for construction material takeoffs.

Instructions

[quantity-takeoff — auditable construction material takeoffs (locked waste + purchase rounding)] List the bundled material pack version, digest, coverage, shapes, rebar sizes, roof pitches, and explicit unsupported policy.

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__list_material_pack"
  }
}

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: +"list_material_packArguments"
  2. Changed2 schema fields changedv0.1.9
    • addedInput schema / required
      Added value: +[]
    • removedInput schema / title
      Removed value: -"list_material_packArguments"
  3. Addedv0.1.6

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It mentions the output attributes but fails to describe side effects, authentication needs, pagination, or any constraints. As a non-destructive list operation, the behavior is mostly implied, but the description lacks explicit transparency.

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 description is a single sentence after a domain prefix, which is concise and front-loaded. The bracket prefix may be extraneous, but the core description is tight with no wasted words.

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 simple list tool with no parameters and no output schema, the description covers the main returned attributes. However, it lacks mention of pagination, return format, or any filtering capabilities, leaving some gaps in completeness.

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 input schema has zero parameters, so no parameter explanation is needed. The description adds value by listing the attributes returned (version, digest, etc.), which compensates for the lack of an output schema. Baseline for 0 params is 4.

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

Purpose5/5

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

The description clearly states the tool's purpose: listing bundled material packs with specific attributes like version, digest, coverage, shapes, etc. The verb 'List' and resource 'material pack' are precise, and it distinguishes from sibling tools like 'get_material_pack' and 'list_assemblies'.

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?

The description does not provide any guidance on when to use this tool versus alternatives such as 'get_material_pack' or 'list_assemblies'. No usage context, prerequisites, or exclusions are mentioned.

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