Skip to main content
Glama

Creative Commons attribution snippet

bpj_creative_commons_attribution
Read-onlyIdempotent

Create an escaped attribution paragraph from work title, creator, source and a Creative Commons license URL.

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": {
      "name": "<name>",
      "author": "<author>",
      "url": "<url>",
      "license": "<license>"
    },
    "name": "bpj_creative_commons_attribution"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
nameYes
authorYes
licenseYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The word 'escaped' adds real behavioral context about the output, but the description never says which escaping scheme (Markdown, HTML, plain) is applied or what the returned string looks like. That omission is meaningful for a formatting tool.

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?

A single front-loaded sentence with no filler; the output artifact is named first and the inputs follow. It is efficient, though slightly under-specified for a four-parameter tool with no schema documentation.

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?

For a low-complexity, closed-world, non-destructive formatter with strong annotations, the definition is adequate to call correctly. It leaves open the escaping target and the exact output shape, which are the two things an agent would still want to know.

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 0%, so the description carries the full burden, and it does map the four fields to roles (work title, creator, source, CC license URL) that the bare schema titles only partly convey. It stops short of saying whether the license must be a canonical creativecommons.org URL or whether URL fields need scheme/host constraints.

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 gives a specific verb ('Create') and a specific resource ('escaped attribution paragraph'), and it enumerates the inputs that feed it. It doesn't distinguish itself from nearby attribution-related siblings, but an agent can tell what output to expect.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. The agent must infer from the name alone that this is for building a CC credit line rather than, say, a markdown snippet.

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.