Skip to main content
Glama

Accept the Outbound Compliance Agreement

accept_outbound_agreement

Accept the agreement on your person's behalf ONLY after they have read it and told you they agree. Requires their full name as they typed it; recorded with this connection. Admin or manager only.

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": {
      "version": "<version>",
      "full_name": "<full_name>",
      "person_agreed": "<person_agreed>"
    },
    "name": "accept_outbound_agreement"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYesVersion from get_outbound_agreement.
full_nameYesThe accepting person's first and last name, as they typed it.
person_agreedYestrue only if your person explicitly said they agree.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/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 real weight here: it discloses the consent precondition, the role requirement, and that the acceptance is 'recorded with this connection,' signaling a durable, attributable legal record. It does not state whether acceptance is reversible or what happens on a duplicate call, which matters for a consent-record action.

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?

Three tight sentences with the safety-critical precondition front-loaded ahead of mechanical details. Minor redundancy in restating the full-name requirement that the schema already covers, but no filler.

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?

All three required parameters are documented in the schema, and the description supplies the consent, role, and attribution context that the annotations do not. No output schema exists, but the missing piece is what a successful acceptance returns and whether it can be undone.

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%, and the schema already documents the version source (get_outbound_agreement) and the 'as they typed it' wording. The description restates the name requirement and reinforces the intent of person_agreed rather than adding new meaning, so the baseline 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 states a specific verb and resource (accept the outbound compliance agreement) and makes the contrast with get_outbound_agreement clear through the precondition that the person must have read it first. It stops short of naming the sibling by name, so an agent must infer the read-then-accept sequence.

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?

Strong gating guidance: 'ONLY after they have read it and told you they agree' plus a role restriction ('Admin or manager only') defines both when and when-not to call. The alternative path — fetching the agreement first via get_outbound_agreement — is only implied, not named.

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.