Skip to main content
Glama

Parse a Software Heritage core identifier

bpj_swhid_core_components
Read-onlyIdempotent

Validate a version 1 Software Heritage core identifier and report its archival object type and hexadecimal digest.

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": {
      "value": "<value>"
    },
    "name": "bpj_swhid_core_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds what is produced (object type and hex digest) and implicitly scopes to the 'core' form only, excluding qualified/with-context SWHIDs, but it never states what happens on an invalid identifier (error vs. a false/invalid result).

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

Conciseness5/5

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

A single front-loaded sentence with no filler. The verb and the returned fields are both stated within the minimum word count.

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 one-parameter validation tool with no output schema, the description does state the reported fields, which is helpful. It still leaves the failure case and the accepted input format unspecified, which are the two things an agent most needs 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 coverage is 0% for the single 'value' parameter, so the description carries the burden: it tells the agent the value is a version 1 Software Heritage core identifier. It does not describe the expected syntax (scheme prefix, object-type segment, hash length) or the 240-character limit's implications.

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?

Specific verb plus specific resource: 'Validate a version 1 Software Heritage core identifier and report its archival object type and hexadecimal digest.' The version restriction ('version 1') and 'core identifier' scope make it distinct from generic identity tools in the sibling set, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the verb 'Validate' — call it when you have a SWHID string to check — but there is no explicit when-to-use/when-not guidance and no mention of how it relates to the other identifier tools visible in the sibling list.

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.