Skip to main content
Glama

List registry embeds

list_registry_embeds
Read-only

A project's terms and claims put on other sites (PM-1165–PM-1168), and its sets: for each, its id, 'kind' (term, claim or set), 'name' (the term's word, the claim's label, the set's name), the ready code — 'script' (the cloud's script, once per page), 'mark' (the words on the site that open the cloud) and, for one thing, 'iframe' (a card) and 'url' — the sites allowed to show it (empty is any), the term ('expiresAt', null until removed), who made it and when, and how many times it was opened, 'lang' — the language it shows the words in (null: as written) — and 'askedLangs', the languages pages asked it for, kept translated too. A set lists what it names in 'items'; a term on it you may not open is only counted in 'hidden'. Only for somebody who may write in the project.

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": {
      "project": "<project>"
    },
    "name": "list_registry_embeds"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesThe project key, e.g. MATH.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds the write-permission requirement and the 'hidden' behavior (items you may not open are only counted), which are genuine behavioral facts beyond the annotations. However, it says nothing about volume, ordering or pagination for what is presumably an unbounded list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The entire description is one sprawling run-on sentence built from em dashes, quoted field names and nested parentheticals, so nothing is front-loaded and the reader must parse to the end to learn the permission constraint. Field-by-field detail is packed in without any structural hierarchy, making it hard to scan.

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?

There is no output schema, so the description legitimately carries the return-value burden and does enumerate id, kind, name, ready code, url, expiresAt, authors, open counts, lang/askedLangs, items and hidden. That makes it roughly adequate for a read-only single-parameter tool, but the coverage is delivered so opaquely that an agent cannot easily reconstruct the response shape or ordering.

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?

With a single parameter at 100% schema description coverage ('The project key, e.g. MATH.'), the schema already carries the semantics and the description adds nothing about the project argument — not even how it relates to the returned embeds. Baseline 3 applies.

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

Purpose3/5

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

The subject matter (a project's terms, claims and sets embedded on other sites) is specific, but the description never states an explicit verb like 'list' or 'returns' — it opens with a noun phrase and immediately dives into field enumeration. It also gives no signal distinguishing it from the sibling list_wiki_embeds, so an agent must infer the boundary between the two.

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 explicit when-to-use guidance and no named alternative (e.g. list_wiki_embeds, get_registry_translations) for related lookups. The only eligibility statement is the trailing 'Only for somebody who may write in the project', which is a permission gate rather than usage guidance.

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