Skip to main content
Glama

Ranked item list metadata

bpj_itemlist_ranked_metadata
Read-onlyIdempotent

Turn name and URL rows into an ordered ItemList with one-based positions.

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>",
      "items": "<items>"
    },
    "name": "bpj_itemlist_ranked_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
itemsYes

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, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that — ordering is preserved and positions are one-based — but says nothing about output serialization (e.g. whether the ItemList is JSON-LD/Schema.org markup) or handling of malformed rows.

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 tight sentence with the outcome front-loaded and no filler. It is efficient, though the compression of "name and URL rows" leaves the row format slightly ambiguous.

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 simple two-parameter, read-only tool this is close to adequate, but with no output schema and no schema descriptions at all, the description should have said what the returned ItemList looks like and how positions are assigned. As written, an agent knows the intent but not the concrete contract.

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 real weight here. It clarifies that items are name-and-URL pairs supplied as rows, which is the key semantic, but it does not specify the row delimiter or what the top-level name parameter represents in the produced ItemList.

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 transformation: rows of name/URL data become an ordered ItemList with one-based positions. That distinguishes it from the many metadata siblings (book, product, podcast, etc.) that each map a different resource type, though it never explicitly contrasts itself with them.

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?

No guidance on when to reach for this tool instead of the other metadata builders, no prerequisites, and no note on what input rows are valid. The agent must infer usage purely from the verb and the parameter names.

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.