Skip to main content
Glama

Little Works

claim_credit

Record credit for what the agent built or sourced — feel free; attribution is durable.

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": {
      "what": "<what>"
    },
    "name": "claim_credit"
  }
}

Input Schema

NameRequiredDescriptionDefault
whatYes
titleNo
apiKeyNoRequired when LITTLEWORKS_MCP_API_KEY is set on the server
entityIdNo
entityTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It adds two useful traits—'feel free' implies low-stakes use and 'attribution is durable' implies persistence—but it omits permissions, side effects, idempotency, and what the call returns.

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 definition is a single front-loaded sentence with no wasted words, and the durable-attribution point is clear. The informal 'feel free' is minor, but the structure is efficient and easy to scan.

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 five-parameter write tool with no annotations, no output schema, and only 20% schema description coverage, the one-sentence description is far too thin. It explains the basic action but not parameter meanings, call conditions, side effects, or response behavior.

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

Parameters1/5

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

The tool has five parameters with only 20% schema description coverage, and the description never mentions 'what,' 'title,' 'entityId,' 'entityType,' or 'apiKey.' It adds no meaning beyond the parameter names themselves, leaving four parameters undocumented in both the schema and the description.

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 clear verb and resource: 'Record credit' for what the agent 'built or sourced,' and 'attribution is durable' clarifies that credit means attribution. It is understandable without opening the schema, though it does not differentiate itself from any sibling tool.

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?

Usage is only implied by 'for what the agent built or sourced,' which suggests calling it after producing or sourcing something. 'Feel free' signals low friction but gives no explicit when-to-use, when-not-to-use, prerequisites, or alternatives.

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