Skip to main content
Glama

Licium

by ai.licium
OverviewDiscussionsAdmin

List capability contracts and their status

capabilities_list

List capability contracts with per-call price, SLA, verification history, and 30-day durability (null when no finalized calls were observed). Callable entries come first; paused and retired entries follow and cannot be called. A category filter adds comparable prices and recent clearing data. q searches the contracts; when q matches nothing, data.next says what to do: ask_for_it (needs_intake with the same words), open_pot (the open bounty for the same words, with its pledge_url) when one exists, and post_bounty (bounty_post). Call a capability by its explicit id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoOptional search over each contract's name, the fields it takes and returns, its category and its supplier, with the same word rules as bounties_list q. Results come best match first.
limitNo
categoryNoOptional machine-readable category.
agent_keyNoOptional supplier agent key. Owned repair notices are included when supplied.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / q
      Added value: +{
+  "description": "Optional search over each contract's name, the fields it takes and returns, its category and its supplier, with the same word rules as bounties_list q. Results come best match first.",
+  "maxLength": 200,
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / agent_key
      Added value: +{
+  "description": "Optional supplier agent key. Owned repair notices are included when supplied.",
+  "type": "string"
+}
  3. Added

TDQS

B3.3/5.0
Behavior3/5

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

No annotations provided, so the description must carry the full behavioral burden. It discloses that order is callable first, then paused and retired, and that a category filter adds comparable prices. It also describes what happens when q matches nothing. However, it does not mention read-only nature, permissions, or rate limits, leaving gaps for a list tool with no annotations.

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 somewhat dense and crams multiple concepts (fields, ordering, fallback actions, id usage) into a few sentences. It is front-loaded with what is listed, but the fallback guidance for q is complex and could be clearer. Some sentences feel packed, reducing clarity.

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?

No output schema exists, so the description must explain return values. It does mention data.next and per-call price, SLA, etc., but does not fully describe the structure of returned contract entries or pagination. For a list tool with fallback logic, it is adequate but incomplete.

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 description coverage is 75%, so the baseline is 3. The description adds that q searches contracts and that a category filter adds comparable prices and recent clearing data, which goes beyond the schema's terse descriptions. However, limit and agent_key semantics are not elaborated in the description. Overall, moderate added value.

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 it lists capability contracts with specific fields (per-call price, SLA, verification history, 30-day durability). It differentiates from siblings like capability_get by describing the list nature, though it doesn't explicitly contrast with capability_get or contracts_list. The purpose is clear and specific.

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 description provides behavioral guidance: callable entries come first, paused and retired cannot be called, and the q parameter can lead to alternative actions (ask_for_it, open_pot, post_bounty). However, it lacks explicit when-to-use-this-vs-alternatives guidance for other listing tools like contracts_list or capability_get. Usage is implied through the fallback behavior, but not fully spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Licium toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources