Skip to main content
Glama

Intakra Buying Signals and Workspace

Suggested accounts

list_suggestions
Read-onlyIdempotent

Use for 'which accounts did Intakra suggest?'. Returns companies Intakra suggested adding to the list (from filings, news and lookalikes of your customers), each with the reason. Suggestions do not count toward the plan until approved in Intakra.

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

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 25.
stateNoDefault pending.

Output Schema

NameRequiredDescriptionDefault
suggestionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "suggestions": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "country": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "domain": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "employee_count": {
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "industry": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "name": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "reason": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "source": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "state": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "suggestions"
      +  ],
      +  "type": "object"
      +}
  2. Added
  3. Removed
  4. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description is free to add domain context — and it does: where suggestions originate, that each carries a reason, and the plan-billing implication of unapproved suggestions. It doesn't describe ordering, volume limits, or what the reason field looks like, which keeps it from a 5.

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 short sentences, front-loaded with the natural-language trigger phrase, then the payload, then the caveat. Each sentence contributes, though the lead-in is phrased as a quoted query rather than a direct statement of purpose, which reads slightly awkwardly.

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?

An output schema exists, so return-shape detail is not required, and the description still flags the key returned field (the reason). For a two-parameter read tool this is close to complete; the only real gap is that the state filter's usefulness is left for the agent to discover in the schema.

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?

With 100% schema description coverage, the schema already documents the limit default (25) and the state enum default (pending). The description adds nothing about either parameter — notably it never mentions that results can be filtered by pending/approved/rejected state, so parameter meaning comes entirely from the schema.

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 resource (companies Intakra suggested adding to the list) and a concrete verb/outcome (returns them, each with the reason). It also states provenance (filings, news, lookalikes of your customers), which distinguishes it from list_accounts, which returns the actual list rather than proposals.

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?

The opening 'Use for "which accounts did Intakra suggest?"' gives an explicit trigger condition, and the closing note that suggestions don't count toward the plan until approved implies the pending-vs-approved distinction. It stops short of explicitly naming the sibling to use for approving or adding suggestions, so routing is clear in one direction only.

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