Skip to main content
Glama

Intakra Buying Signals and Workspace

Find accounts for me

request_accounts

Use when the user asks Intakra to find companies, and ask first. Requests account suggestions from a short description, an industry, a size range, a country, or up to 5 customer domains. Runs in the background; results arrive later as suggestions (list_suggestions) and never count toward the plan until approved. A few requests a day at most.

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

Input Schema

NameRequiredDescriptionDefault
regionNoUS state or region code
countryNoTwo letter country code, for example US
industryNo
descriptionNoFor example "logistics software companies in Texas"
employee_maxNo
employee_minNo
lookalike_domainsNoUp to 5 customer domains to find lookalikes of

Output Schema

NameRequiredDescriptionDefault
statusYesqueued when the request was accepted.
request_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "request_id": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "status": {
      +      "description": "queued when the request was accepted.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status"
      +  ],
      +  "type": "object"
      +}
  2. Added
  3. Removed
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: the call is asynchronous ('runs in the background'), the output surfaces via list_suggestions, suggestions don't consume plan quota until approved, and there is a rate limit of 'a few requests a day at most'. These are exactly the non-obvious traits an agent needs; only the exact quota/approval mechanics remain unspecified.

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?

Four tight sentences, front-loaded with the usage trigger, then inputs, then async behavior, then the quota constraint. No filler and each sentence carries distinct information.

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?

With an output schema present, the description needn't explain return values, and it still covers the async result path, approval gate, and rate limit. Only the approval workflow details (who approves, how) are left implicit, which is minor for a request-creation tool.

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?

Schema coverage is 57%, and the description compensates by mapping intent categories (short description, industry, size range, country, up to 5 customer domains) onto the parameters, including the 5-domain cap. It omits the region parameter, which the schema covers only minimally.

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?

States a specific verb and resource ('Requests account suggestions') and enumerates the input dimensions (description, industry, size range, country, customer domains). It also distinguishes itself from list_suggestions by naming that sibling as where results later arrive.

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 when the user asks Intakra to find companies, and ask first' gives both a trigger and a mandatory confirmation prerequisite before calling. It does not state exclusions (e.g., when to use add_accounts or list_accounts instead), so it falls short of the full when/when-not bar.

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