Skip to main content
Glama

Physical Capability Cloud

create_investment_pool

Create an investment pool for a capability bounty.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "capabilityType": "<capabilityType>",
      "description": "<description>"
    },
    "name": "create_investment_pool"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyNoCurrency for the pool
descriptionYesDescription of the capability pool
targetAmountNoFunding target amount
capabilityTypeYesType of capability to invest in (e.g. cnc-milling, sla-printing)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a non-destructive write. Beyond that, the description adds nothing: it does not say whether creation is idempotent, who may create a pool, what the initial state is, or what happens if targetAmount or currency is omitted.

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?

It is a single front-loaded sentence with no filler, which is structurally sound. The brevity is under-specification rather than efficiency, since nothing beyond the name is conveyed.

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?

This is a four-parameter mutation with no output schema and no annotation coverage of permissions or side effects. The description omits optional-parameter behavior, the identity of the created pool, and any prerequisite for a capability to exist, leaving real gaps for an agent to call it correctly.

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 100%, including an enum for currency and examples for capabilityType, so the schema carries the parameter burden and baseline 3 applies. The description contributes no additional meaning, and its phrase "capability bounty" slightly diverges from the schema's "capability pool" terminology.

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 a concrete verb and resource: "Create an investment pool," scoped to "a capability bounty." That is enough for an agent to know what the tool produces. It does not, however, distinguish this from siblings such as convert_bounty_to_pool or create_capability, which plausibly touch the same domain.

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?

There is no guidance on when to create a pool versus converting an existing bounty into one, nor any stated prerequisites such as existing capability, funding, or authorization. The agent must infer the selection conditions from the name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.