Skip to main content
Glama

Image credit and license metadata

bpj_image_credit_metadata
Read-onlyIdempotent

Build ImageObject metadata with creator, license URL and credit text.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
authorYes
creditYes
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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the output is composed metadata, but says nothing about whether an ImageObject is returned as JSON-LD, how invalid or over-length license URLs are handled, or what errors look like. Useful, but thin given there is no output schema.

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 intent is immediate. It is efficient rather than padded, though it is brief enough to edge into under-specification.

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 four-required-parameter, no-output-schema builder, the definition should at least cover what is returned and the role of the page URL. Annotations handle the safety side, but the return shape and the undocumented 'url' parameter leave real gaps.

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 only semantics come from field titles and this sentence, which maps 'author' to schema.org creator, 'license' to license URL, and 'credit' to credit text. It never explains the 'url' parameter (Page URL), leaving one of four required inputs without any semantics in either schema or 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 gives a specific verb and resource ('Build ImageObject metadata') plus the fields it populates (creator, license URL, credit text), which cleanly separates it from sibling metadata builders such as bpj_video_thumbnail_metadata or bpj_product_gtin_metadata. It stops short of naming an alternative, so it lands at 4 rather than 5.

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 (e.g., that all four fields must be known before calling), and no mention of when a caller should skip this tool. The only steering is what the name and purpose sentence imply.

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.