First AI Employee

Get connected business

get_business_identity

Read-onlyIdempotent

Use this first to confirm which First AI Employee business is connected and which bounded MCP capabilities are currently available. Signature approval capabilities prepare and record local approval only; they never send envelopes or sign documents. It returns no customer ID, owner email, or secret.

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": "get_business_identity"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`business`	Yes
`request_id`	Yes
`schema_version`	Yes
`available_capabilities`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds genuine context beyond that: the explicit privacy boundary (no customer ID, owner email, or secret returned) and the warning that signature approval capabilities only prepare and record local approvals rather than sending or signing. That caveat is important framing for interpreting the capability list, though it is more about a capability than about this call.

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 the actionable 'use this first' instruction. The middle sentence about signature approval capabilities is arguably tangential to a business-identity call, but it earns its place by preventing a misreading of the returned capability list.

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 zero-parameter read with an output schema, the description covers purpose, call ordering, and the privacy boundary of the response, which is enough to invoke it correctly. The only remaining gap is that it does not clarify the division of labor with get_capabilities, which matters given the overlap in what it claims to return.

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 the baseline is 4 and there is no parameter meaning the description could add or omit. Schema coverage is 100% with additionalProperties false, so nothing is left ambiguous.

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 and resource: confirm which business is connected and which bounded MCP capabilities are available. It is clear on its own, but the phrase about 'which bounded MCP capabilities are currently available' overlaps with the sibling get_capabilities, so an agent cannot fully separate the two from the description alone.

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?

'Use this first' gives explicit ordering guidance relative to the rest of the toolset, which is real routing value. It stops short of naming get_capabilities as the alternative or stating when-not to call it, leaving the sibling relationship to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All First AI Employee tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?