Skip to main content
Glama

Submit an identity protection intake

submit_identity_protection_intake

Submit an identity protection intake to the firm for matters like online impersonation, stolen photos, deepfakes, BIPA violations, or false reviews. IMPORTANT: only call this with the user's explicit consent; the firm will contact them directly. Requires name, phone, and email.

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": {
      "name": "<name>",
      "phone": "<phone>",
      "email": "<email>"
    },
    "name": "submit_identity_protection_intake"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull name
emailYesContact email address
phoneYesContact phone number
descriptionNoOne-paragraph summary: what happened, where the content appears, what outcome the user wants

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already signal a non-read-only, open-world, non-idempotent call; the description adds the meaningful detail that this triggers direct outreach from the firm and that consent is mandatory. It does not cover duplicate-submission behavior beyond what idempotentHint=false implies, but the consent and external-contact disclosure is real added value.

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 sentences, front-loaded with purpose, then the consent caveat, then requirements. The closing sentence slightly restates the required fields from the schema, but overall there is little waste.

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 no-output-schema intake form, the description supplies the essential context: what gets submitted, who receives it, and that the firm follows up directly. The main remaining gap is what confirmation or next steps the agent should relay after submission.

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 description only reiterates that name, phone, and email are required — information the schema already carries. It adds no explanation of the optional 'description' field or formatting expectations beyond what the schema provides, so baseline 3 applies.

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 and resource ('submit an identity protection intake') and enumerates the matter types it covers (impersonation, stolen photos, deepfakes, BIPA, false reviews). An agent can immediately tell what this tool does and when it applies.

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 gives a clear precondition ('only call this with the user's explicit consent') and notes the firm will contact the user directly, which shapes when to use it. It does not name alternatives, but none of the listed siblings are close substitutes for this intake, so the guidance is adequate.

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