Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getIdentity

Read-onlyIdempotent

Retrieve the identity and account details linked to a Follow Up Boss API key, enabling you to verify which account the key belongs to.

Instructions

Get identity/account information for the API key

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getIdentity"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds only that the returned identity is tied to the calling API key, which is useful auth context but does not describe what fields come back or whether it can fail for a revoked key. Modest added value beyond 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?

A single short sentence with the key qualifier front-loaded and no wasted words. The only blemish is the hedged 'identity/account' phrasing, which slightly blurs what the resource actually is.

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

Completeness3/5

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

With no output schema and no parameter schema to lean on, the description is the sole source of information about the response, and it says nothing about shape, fields, or error behavior. For a trivial no-arg read this is acceptable but leaves a real gap around return values.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The input schema is empty and fully consistent with that.

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?

States a specific verb+resource ('Get identity/account information') and scopes it to the API key, so the agent knows it is not fetching an arbitrary account. It does not, however, distinguish itself from the sibling getCurrentUser, which reads as near-identical in intent.

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?

The phrase 'for the API key' implies this is the credential-level identity lookup, which is the only usage signal given. There is no explicit when-to-use, when-not-to-use, or statement of how it differs from getCurrentUser or getUser, leaving the choice to inference.

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