Skip to main content
Glama

Add to CRM

Get account

get_account
Read-onlyIdempotent

Show the Add to CRM account this connection belongs to: which CRM is connected, how many lookup credits are left, and anything that will currently stop a lookup or an add.

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_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
crmNothe connected CRM; absent when none is connected
nameNothe customer's name
emailNothe customer's e-mail address
creditsYeslookup credits available; one is spent for each work e-mail address found
no_crm_modeYestrue when the customer works without a CRM, saving people to lists instead
restrictionsYesstable codes for anything that will refuse right now: account_inactive, email_not_verified, no_credits, no_crm_connected, crm_needs_reconnect
credits_sharedYestrue when the lookup credits are one balance shared by the customer's whole team, so credits is the team's and not only the customer's own
email_verifiedYeswhether the customer has confirmed their e-mail address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / credits_shared
      Added value: +{
      +  "description": "true when the lookup credits are one balance shared by the customer's whole team, so credits is the team's and not only the customer's own",
      +  "type": "boolean"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "no_crm_mode",
      -  "credits",
      -  "email_verified",
      -  "restrictions"
      -]New value: +[
      +  "no_crm_mode",
      +  "credits",
      +  "credits_shared",
      +  "email_verified",
      +  "restrictions"
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context — and it does, by disclosing the three things returned, including diagnostics ('anything that will currently stop a lookup or an add'), which tells the agent this call can surface blocking conditions. It stops short of saying what happens in an unauthenticated/unconfigured state.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the object of the call, with the three returned items enumerated in priority order. No filler and no restatement of the tool name.

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?

A no-parameter, read-only tool with full annotations and an output schema — the description needs only to establish what question this answers, and it does. The only residual gap is the absence of any hint about failure/auth states or how the returned 'blockers' should be acted on.

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 schema baseline is 4; there is nothing for the description to clarify and it correctly does not invent parameters.

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?

Names a specific verb ('Show') and resource (the Add to CRM account tied to this connection), and enumerates the payload: connected CRM, remaining lookup credits, and current blockers. That is far more concrete than a generic 'get account', though it never distinguishes itself from the nearest sibling, get_profile, which an agent could plausibly pick instead.

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?

Usage is only implied — an agent infers this is a pre-flight/status check worth calling before a lookup or add. There is no explicit statement of when to call it, when not to, or how it relates to search_crm / get_profile / the add_* tools.

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.