Skip to main content
Glama
Sign In
AgentaOS

AgentaOS

Official
by AgentaOS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Submit verification

agenta_verify_submit

Submit business or individual verification details for review so an AgentaOS merchant can accept live payments; returns the new verification state.

Instructions

Submit business verification so the merchant can accept live payments. Sends the business or individual details for review so the account can take live payments. Required: legalName, country, street, city, url, acceptDeclaration true, and registrationNumber when entity is business. Only set acceptDeclaration after the merchant has read agenta_verify_declaration. Returns the new verification state.

Input Schema

NameRequiredDescriptionDefault
urlNoThe merchant project page
cityNoCity
entityNobusiness | individual (default business)business
postalNoPostal code
streetNoRegistered address
volumeNounder_1k | 1k_10k | 10k_50k | over_50k
countryNoCountry of registration, 2-letter code
businessNoAct for this business you manage (its id). Omit to act as yourself.
categoryNosaas | digital | services | marketplace | physical | other
deliveryNoinstant_digital | email_delivery | subscription_access | manual | scheduled_service | physical_shipped | other
customersNoThe merchant already has paying customers
legalNameNoRegistered company name, or full legal name
descriptionNoOne sentence on what it does
displayNameNoName buyers see on their statement (default --legal-name)
usageClaimsNoThe site shows reviews or user counts
addressCountryNo2-letter code (defaults to --country)
acceptDeclarationNoAttest to the five statements and that the merchant sells none of the not-supported categories (agenta verify declaration)
registrationNumberNoCompany registration number (business only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.3
    • changedInput schema / properties / acceptDeclaration / description
      Previous value: -"Attest to the five statements (agenta verify declaration)"New value: +"Attest to the five statements and that the merchant sells none of the not-supported categories (agenta verify declaration)"
    • addedInput schema / properties / business
      Added value: +{
+  "description": "Act for this business you manage (its id). Omit to act as yourself.",
+  "minLength": 1,
+  "type": "string"
+}
    • removedInput schema / properties / restricted
      Removed value: -{
-  "description": "The merchant sells a regulated or restricted activity",
-  "type": "boolean"
-}
  2. Changed3 schema fields changedv0.1.1
    • changedInput schema / properties / acceptDeclaration / description
      Previous value: -"Attest to the five statements and that the merchant sells none of the not-supported categories (agenta verify declaration)"New value: +"Attest to the five statements (agenta verify declaration)"
    • removedInput schema / properties / business
      Removed value: -{
-  "description": "Act for this business you manage (its id). Omit to act as yourself.",
-  "minLength": 1,
-  "type": "string"
-}
    • addedInput schema / properties / restricted
      Added value: +{
+  "description": "The merchant sells a regulated or restricted activity",
+  "type": "boolean"
+}
  3. Changed3 schema fields changedv0.1.2
    • changedInput schema / properties / acceptDeclaration / description
      Previous value: -"Attest to the five statements (agenta verify declaration)"New value: +"Attest to the five statements and that the merchant sells none of the not-supported categories (agenta verify declaration)"
    • addedInput schema / properties / business
      Added value: +{
+  "description": "Act for this business you manage (its id). Omit to act as yourself.",
+  "minLength": 1,
+  "type": "string"
+}
    • removedInput schema / properties / restricted
      Removed value: -{
-  "description": "The merchant sells a regulated or restricted activity",
-  "type": "boolean"
-}
  4. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds process context beyond that: the details go to a review queue and the call returns the new verification state. It does not say what happens on rejection, how long review takes, or whether submission can be undone short of resubmitting.

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?

Four sentences, but the first two are near-duplicates ('so the merchant can accept live payments' / 'so the account can take live payments'), which wastes the highest-value position. The required-field list and the declaration prerequisite are front-loaded reasonably well.

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 an 18-parameter mutation with no output schema, the description covers the action, the prerequisite, the required subset, and the return value shape. Remaining gaps are the undocumented optional parameters and the review/approval lifecycle, which the schema text carries only partially.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds information the schema does not carry: the required field set (legalName, country, street, city, url, acceptDeclaration) and the conditional requirement of registrationNumber when entity is business. This materially compensates for the schema's empty required list.

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 gives a specific verb and resource (submit business verification) plus the business outcome (accept live payments). It names agenta_verify_declaration as a related sibling, but does not distinguish itself from agenta_verify_status or agenta_verify_resubmit, so an agent must still infer the boundary.

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?

It states the enabling condition (so the account can take live payments) and imposes an explicit sequencing rule: only set acceptDeclaration after the merchant has read agenta_verify_declaration. There is no guidance on when to use this versus verify_status/verify_resubmit, but the prerequisite routing is genuinely useful.

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