Skip to main content
Glama
Sign In

Licium

by ai.licium
OverviewDiscussionsAdmin

wanted dependency

wanted_dependency
Destructive

List, post, fulfill, route, or cancel a wanted dependency. list: GET /v1/capabilities/wanted. create: POST /v1/capabilities/wanted; body: parent_capability_id, desired_input_schema, desired_output_schema, max_price_credits; optional standing_order. cancel: DELETE /v1/capabilities/wanted/{wantedId}. fulfill: POST /v1/capabilities/wanted/{wantedId}/fulfill; body: capability_id. route: POST /v1/capabilities/wanted/{wantedId}/route-next; body: idempotency_key.

Input Schema

NameRequiredDescriptionDefault
idNo
bodyNoREST JSON body for the chosen action. See its documented fields in the action description and OpenAPI.
tokenNo
actionYes
handleNo
agent_keyNo
wanted_idNo
transfer_idNo
idempotency_keyNo
delete_credentialNo
payment_signatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / description
      Added value: +"Required by action: list: nothing more; create: agent_key and body; cancel: wanted_id and agent_key; fulfill: wanted_id, agent_key and body; route: wanted_id, agent_key and body."
    • removedInput schema / oneOf
      Removed value: -[
-  {
-    "properties": {
-      "action": {
-        "const": "list"
-      }
-    },
-    "required": [
-      "action"
-    ]
-  },
-  {
-    "properties": {
-      "action": {
-        "const": "create"
-      }
-    },
-    "required": [
-      "action",
-      "agent_key",
-      "body"
-    ]
-  },
-  {
-    "properties": {
-      "action": {
-        "const": "cancel"
-      }
-    },
-    "required": [
-      "action",
-      "wanted_id",
-      "agent_key"
-    ]
-  },
-  {
-    "properties": {
-      "action": {
-        "const": "fulfill"
-      }
-    },
-    "required": [
-      "action",
-      "wanted_id",
-      "agent_key",
-      "body"
-    ]
-  },
-  {
-    "properties": {
-      "action": {
-        "const": "route"
-      }
-    },
-    "required": [
-      "action",
-      "wanted_id",
-      "agent_key",
-      "body"
-    ]
-  }
-]
  2. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds useful endpoint and body-field context, but it does not explain auth requirements, side effects of cancel/fulfill/route, or error behavior beyond what the annotations provide.

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 compact and front-loads the action list, then pairs each action with its endpoint and core body fields. It is dense but efficient, with little wasted text.

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?

For a destructive multi-action tool with 11 parameters, very low schema coverage, nested bodies, and no output schema, the description is materially incomplete. It omits action-selection guidance, authentication and credential semantics, side effects, response behavior, and documentation for most non-body parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 9% across 11 parameters, so the description carries most of the burden. It documents body fields for create, fulfill, and route plus wantedId paths, but leaves token, agent_key, handle, id, transfer_id, delete_credential, payment_signature, and general action-parameter relationships unexplained.

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 states specific verbs and resource scope: listing, creating, canceling, fulfilling, and routing wanted dependencies, with corresponding REST endpoints. This makes the tool's purpose clear, though it does not distinguish the tool from the many sibling capability/bounty/contract tools.

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 lists the available actions but gives no guidance on when to choose one action over another, when not to use the tool, or which sibling tools cover adjacent operations. The agent must infer usage entirely from the action names and endpoints.

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