Skip to main content
Glama
verifyax

VerifyAX MCP

Official
by verifyax
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Register agent

register_agent

Add an AI agent to VerifyAX by providing its name, connector type, and endpoint URL, with optional auth settings. Checks connectivity for A2A, Direct Line, and MCP agents and returns the new UUID.

Instructions

Registers an AI agent in VerifyAX given its name, connector type (A2A, API, DIRECTLINE for Copilot Studio, or MCP), URL, and optional auth or connector settings. For A2A agents it first verifies the agent card is reachable; DIRECTLINE and MCP agents are probed before creation. Returns the new agent’s uuid and whether connectivity was checked. Note: any token, Direct Line secret, or password passed here transits the conversation — prefer supplying credentials out of band where possible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mcpNo
nameYesWorkspace-unique agent name.
tokenNoToken for bearer/cs auth. Sensitive — see the note in the tool description.
timeoutNoRequest timeout in milliseconds.
agent_urlNoEndpoint URL. Required for A2A, API, and MCP (catalogue adapter A2A URL). Optional for DIRECTLINE — derived from region when omitted.
agent_typeNoDefaults to A2A.
directlineNo
auth_methodNo
descriptionNo
agent_card_urlNo
basic_passwordNoSensitive — see the note in the tool description.
basic_usernameNo
agent_card_pathNo
default_output_modesNo
include_full_contextNo
include_message_historyNo
max_requests_per_minuteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.7
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / directline / additionalProperties
      Removed value: -false
    • addedInput schema / properties / max_requests_per_minute / maximum
      Added value: +9007199254740991
    • removedInput schema / properties / mcp / additionalProperties
      Removed value: -false
    • addedInput schema / properties / timeout / maximum
      Added value: +9007199254740991
  2. Addedv1.0.1

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description carries the interesting behavior and does so well: it discloses the pre-creation reachability check for A2A and the probing for DIRECTLINE/MCP, states the return payload (new uuid plus whether connectivity was checked), and warns that credentials transiting the conversation should be supplied out of band. That is meaningful side-effect and security context beyond the annotations.

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?

Four sentences, front-loaded with the core action and connector enumeration before the behavioral and security notes. Dense but each sentence contributes; only slightly longer than strictly necessary.

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

Completeness4/5

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

For a 17-parameter mutation tool with no output schema, the description supplies the return values, connector-specific behavior, and a credential-handling caveat, which covers the agent's main decision points. Remaining gaps are the undocumented optional tuning parameters, which the 35% schema coverage does not fill in either.

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 only 35% across 17 parameters, so the description is expected to compensate. It identifies the primary inputs (name, connector type with its enum values, URL, optional auth/connector settings), which covers the essential fields, but leaves many optional parameters (timeout, include_full_context, max_requests_per_minute, default_output_modes, agent_card_path, etc.) unexplained in either place.

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 names a specific verb (registers) and resource (AI agent in VerifyAX), then enumerates the four connector types (A2A, API, DIRECTLINE, MCP) that shape the call. This cleanly distinguishes it from the read/delete siblings such as list_agents and delete_agent without the agent needing to open any schema.

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?

It explains what happens per connector type (A2A card verification, DIRECTLINE/MCP probing) but never states when to prefer this tool over alternatives or any prerequisites/exclusions. Usage is implied by the connector-type branching rather than made explicit.

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

Deploy Server

Other Tools