Skip to main content
Glama

resource_register

DestructiveIdempotent

Register existing potentials, structures, projects, publications, or environments with provenance and license details to track their origin and reuse rights.

Instructions

Register an existing potential, structure, author project, publication or environment with provenance and license.

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>",
      "kind": "<kind>",
      "location": "<location>",
      "provenance": "<provenance>",
      "op_id": "<op_id>"
    },
    "name": "resource_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
nameYes
op_idYes
locationYes
provenanceYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the description carries a lower bar — but it adds nothing about what registration mutates, whether an existing registration can be overwritten, or how op_id drives idempotency. It also promises 'license' handling that no parameter backs, adding confusion rather than behavioral context.

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?

It is a single front-loaded sentence with no padding, which is structurally fine. However, the five-item resource enumeration is noisy and the 'license' clause is extraneous relative to the actual schema, so the compactness comes at the cost of precision.

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

Completeness2/5

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

An output schema exists, so return values need no explanation. But for a destructive, five-required-parameter tool with a nested provenance object and zero schema descriptions, the definition supplies neither parameter meaning nor mutation/idempotency behavior — a significant shortfall for this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five required parameters, so the description must carry the semantic load and does not: name, kind, location, and op_id are never explained, and the named 'license' has no corresponding property. Only 'provenance' is echoed from the schema, which adds no meaning beyond the field name.

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 verb 'register' plus the qualifier 'existing' gives a recognizable action, but the resource list ('potential, structure, author project, publication or environment') is a cryptic, heterogeneous enumeration with no mapping to the 'kind' parameter. It also never distinguishes itself from sibling registers such as artifact_register, checker_register, or workflow_register, so an agent cannot confidently pick it over 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?

'Register an existing ...' faintly implies the resource must already exist at a location, which is the only usage signal present. There is no explicit when-to-use, when-not-to-use, prerequisite, or named alternative (resource_catalog_import, artifact_register) to route the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.