Skip to main content
Glama

GVRN Incorporation

Submit incorporation request

submit_incorporation
Destructive

Submits a draft for review by the GVRN team and returns the request status. Requires a verificationToken for the email that created the draft, which becomes the contact for the request. Optional fields may be left blank. Irreversible: the draft becomes read-only and a review request is filed with the GVRN team.

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": {
      "draftId": "<draftId>",
      "verificationToken": "<verificationToken>"
    },
    "name": "submit_incorporation"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdYesDraft id returned by create_incorporation_draft
verificationTokenYesToken from verify_email_otp for the email the draft is bound to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / verificationToken / description
      Previous value: -"Token from verify_email_otp"New value: +"Token from verify_email_otp for the email the draft is bound to"
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / draftId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description goes further: it spells out exactly what is destroyed ('the draft becomes read-only'), that a review request is filed, and that the token's email becomes the request contact. That is concrete consequence-level disclosure beyond the annotation flags.

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 short sentences, front-loaded with the action and then the prerequisite and the irreversible consequence. The line 'Optional fields may be left blank' is the weakest — the schema exposes no optional parameters, so it refers obliquely to draft fields and reads as filler.

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

Completeness5/5

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

For a two-parameter, non-idempotent mutation with no output schema, the description covers prerequisite, side effects, reversibility, and return value. An agent has everything needed to decide to call it and to warn about the consequences.

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 both parameters are already documented with their upstream sources. The description adds one real fact — the verification token's email becomes the contact for the request — but nothing about draftId semantics, so the baseline of 3 holds.

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?

States a specific verb and resource ('Submits a draft for review by the GVRN team') plus the return value ('returns the request status'). That cleanly separates it from update_incorporation_draft and get_incorporation_status among the siblings.

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?

Makes the precondition explicit: a verificationToken is required, and the schema ties it to verify_email_otp and the draft to create_incorporation_draft, so the call chain is inferable. It stops short of naming alternatives or saying when NOT to submit (e.g. draft not ready), so it is not a full 5.

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.

Resources