Skip to main content
Glama
Sign In
hwcontract

hwcontract

by MohibShaikh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_contracts

List bundled hardware contract templates, including names, kinds, installed paths, and required capture adapters. No hardware interaction is needed.

Instructions

List bundled contract templates, names, kinds, installed paths, and capture adapter requirements. No hardware.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the read-only, hardware-free nature ('No hardware.') and what the listing contains, but says nothing about pagination, permissions, or whether results are static bundled data versus dynamically discovered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the verb and the returned fields, with the constraint ('No hardware.') placed last where it belongs. No filler.

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 zero-param listing tool with no output schema, the description usefully enumerates the returned fields, which compensates for the absent output schema. Minor gaps remain around what 'kinds' and 'capture adapter requirements' mean in practice.

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 there is nothing for the description to disambiguate; baseline 4 applies.

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?

Specific verb+resource ('List bundled contract templates') with an enumeration of returned fields (names, kinds, installed paths, capture adapter requirements). It is distinguishable from judge_contract, though the distinction is inferred from the verb rather than stated explicitly.

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?

The trailing 'No hardware.' implicitly tells the agent this call is safe without a device attached, but there is no explicit when-to-use statement and no named alternative (e.g. judge_contract) for the contrasting case.

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