Skip to main content
Glama

Little Works

agent_freedom_capabilities

Source materials, sell music, take credit, help people vocalize — agent plug into Little Works.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and does not meet it. It never says whether the call is a safe read, what it returns, or whether the listed verbs describe capabilities being advertised versus actions being executed. The action-flavored phrasing actively invites a wrong mental model for a no-argument tool.

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 short sentence with no padding, which is good. However, the compressed poetic phrasing trades clarity for brevity, so the economy does not pay off in comprehension.

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?

With no output schema and no annotations, the description is the only source of truth about what this call yields, and it does not say. For a capability-discovery tool the agent needs to know it returns a manifest of available actions, which is never stated.

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 the baseline of 4 applies and there is nothing for the description to disambiguate. No parameter semantics are needed or missing.

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

Purpose2/5

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

The description strings together action verbs ("source materials, sell music, take credit, help people vocalize") that read as if the tool performs commerce, then appends the fragment "agent plug into Little Works." It never states that this is a zero-parameter capability manifest, nor how it differs from siblings like discover_capabilities or materials_commerce_capabilities. The purpose is suggestive rather than stated.

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 indication of when an agent should call this instead of discover_capabilities, get_anything_capabilities, or materials_commerce_capabilities. No prerequisites, no exclusions, and no sequencing guidance are given. The agent must guess at routing.

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.

Resources