Skip to main content
Glama

register_discovered

Idempotent

Discovers manifests from entry points and the datasources directory, then registers them so discovered data sources are available for crawldata-engine use.

Instructions

Auto-discover + register manifests from entry points + a datasources/ dir.

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": "register_discovered"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety framing is largely covered. The description does add something not in annotations: the tool reads from entry points and a datasources/ directory, indicating filesystem/environment scanning. It says nothing about what happens to pre-existing registrations, malformed manifests, or partial failures.

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 front-loaded sentence with no padding, but the '+' shorthand and missing article make it read like a commit note rather than a tool specification. It is appropriately short for a zero-parameter tool.

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?

An output schema exists, so return-value description is not required. However, for a mutating, filesystem-scanning registration tool with no inputs to control scope, the agent needs to know what gets scanned, whether existing entries are overwritten, and how errors surface — none of which is addressed.

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

Parameters4/5

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

The tool takes zero parameters and the schema is closed (additionalProperties=false), so there is nothing for the description to disambiguate. Baseline for a parameterless tool applies.

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 names a concrete verb pair ('auto-discover + register') and the resource ('manifests'), plus the two sources it scans: entry points and a datasources/ dir. The 'auto' prefix implicitly separates it from manual registration, but it never names register_datasource or clarifies the boundary, and 'entry points' and 'manifests' remain undefined jargon.

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?

There is no explicit when-to-use or when-not-to-use statement and no mention of the obvious alternative, register_datasource. The 'auto-discover' framing only implies the scenario (bulk automatic registration of already-present manifests versus one-off manual registration), leaving the agent to infer it.

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