Skip to main content
Glama

Create claim embed

create_claim_embed

Put one claim of a project on other sites (PM-1165, PM-1166): a link anybody can open with no account, which shows its kind, number, title, statement with its formulas and status — never its bases, journal or review — and, while the project is public, the page it rests on. Answers with the ready code: 'script' once per page and 'mark' around the words on the site, which open the claim in a cloud, or 'iframe', a card. Name it by 'id', or by 'project' and 'label'. 'sites', 'days' and 'lang' as for create_term_embed. Only for somebody who may write in the project; a line in its history.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_claim_embed"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe claim's id, as list_claims returned it. Or name it by 'project' and 'label'.
daysNoDays the link answers, 1 to 3650. Optional: none is until it is removed.
langNoThe language the link shows the words in, e.g. 'en' (PM-1373): a person's translation where there is one, else the machine's, marked as such. Optional: none shows them as written; a page may still ask for another.
labelNoThe claim's label, e.g. 'thm:d5-rank5', with 'project'.
sitesNoSites that may show it, comma-separated, as https://example.org. Optional: none is any site.
projectNoThe project key, with 'label'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
      +  "default": null,
      +  "description": "The language the link shows the words in, e.g. 'en' (PM-1373): a person's translation where there is one, else the machine's, marked as such. Optional: none shows them as written; a page may still ask for another.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, the description discloses exactly what becomes public: the claim's kind, number, title, statement with formulas and status, and the underlying page while the project is public, but never its bases, journal or review. It also describes the returned code forms ('script', 'mark', 'iframe'), the permission requirement, and that the action is recorded in project history.

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

Conciseness3/5

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

The description is information-dense and front-loads the core action, but it is delivered as a long, heavily punctuated passage that is difficult to parse. Every clause contributes useful facts, yet the structure could be clearer and easier to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a write tool with no output schema, the description covers the necessary behavioral context: what is exposed and hidden, the return formats, permission requirements, audit logging, and how parameters combine. An agent has enough information to call it correctly.

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 100%, and the schema already documents all six parameters, including the id versus project-and-label naming and the sites, days and lang options. The description reinforces the naming choice and cross-references create_term_embed for three parameters, but it adds little semantic detail beyond the schema.

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

Purpose5/5

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

The description states a specific verb and resource: putting one claim of a project on other sites as an embeddable link. It distinguishes the artifact from a generic embed by spelling out what the link shows and what it never exposes, which lets an agent separate it from sibling embed tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear prerequisites: the caller must be somebody who may write in the project, and a line is added to the project's history. It also explains how to name the claim by 'id' or by 'project' and 'label'. It does not explicitly say when to choose this over sibling tools such as create_term_embed or create_wiki_embed, so it falls short of the top score.

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