Skip to main content
Glama

Register or Re-Audit Public MCP/A2A Endpoint

register_agent_endpoint
Idempotent

Submit a public HTTPS MCP or A2A endpoint for immediate live SSRF-guarded Virginia Scout interrogation, 64-bit MGLE-NNP grading, and directory indexing. Use when enrolling a new server or appealing a quarantined grade; do not use for private localhost/RFC1918 URLs.

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": {
      "endpoint": "<endpoint>"
    },
    "name": "register_agent_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idNoOptional canonical slug or identifier (e.g. 'com.example/my-mcp'); generated automatically if omitted.
endpointYesPublicly reachable HTTPS MCP or A2A endpoint URL to interrogate in real time.
descriptionNoOptional summary of capabilities or reason for re-audit.

Output Schema

NameRequiredDescriptionDefault
appeal_idNoAudit log reference ID.
registeredYesTrue when SSRF validation passed and live interrogation completed.
audit_statusYesAssigned Virginia Scout runtime audit status.
updated_recordNoResulting phonebook record and 64-bit coupler.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=true and destructiveHint=false. The description adds real context beyond that: the endpoint will be actively fetched over the network under SSRF guard, graded, and publicly indexed — which tells the agent the submission has lasting public visibility. It stops short of covering rate limits, what happens to a quarantined result, or whether re-submission overwrites an existing entry.

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?

Two sentences, front-loaded with the action and its effects, then the usage/exclusion clause. Dense and largely waste-free, though the stacked marketing-style jargon costs some readability.

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?

With an output schema present and all three parameters documented, the description needn't explain return values, and it does cover the core action and side effects. It leaves open what a quarantine/grading failure means for the caller and how re-audits differ from first enrollments, which matters for a tool whose stated use case includes appeals.

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 100%, so the baseline is 3. The description reinforces the public-HTTPS constraint on 'endpoint' and the re-audit rationale that maps to 'description', but adds no format or validation detail the schema does not already carry.

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?

States a specific verb and resource: submitting a public HTTPS MCP or A2A endpoint, plus the downstream consequences (SSRF-guarded interrogation, grading, directory indexing). The idiosyncratic jargon ('Virginia Scout', 'MGLE-NNP') slightly obscures the plain meaning, but an agent can still tell this is the enrollment/registration tool and not a lookup like get_agent_dossier or search_agent_directory.

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?

Gives an explicit when-to-use ('enrolling a new server or appealing a quarantined grade') and an explicit when-not ('do not use for private localhost/RFC1918 URLs'). It does not name an alternative tool for the excluded case, but no sibling plausibly covers that role, so the guidance is close to complete.

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.