Skip to main content
Glama

Intakra Buying Signals and Workspace

Look up an account

get_account
Read-onlyIdempotent

Use for 'what do we know about acme.com?'. Returns one tracked account: up to 12 recent dated findings with links, and its open leads with dated proof. Pass a domain (acme.com), a company name or an account id. Saved records only, no new check.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account": "<account>"
    },
    "name": "get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountYesDomain, company name, or account id

Output Schema

NameRequiredDescriptionDefault
as_ofNo
accountYes
recent_findingsYes
open_opportunitiesYes
recent_findings_limitNo
recent_findings_truncatedNo
open_opportunities_truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedOutput schema / properties / open_opportunities / items / properties / change_date
      Added value: +{
      +  "description": "YYYY-MM-DD the source dates the change.",
      +  "format": "date",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / open_opportunities / items / properties / checked_date
      Added value: +{
      +  "description": "YYYY-MM-DD Intakra last checked the source.",
      +  "format": "date",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / open_opportunities / items / properties / paste_line
      Added value: +{
      +  "description": "One sentence a rep can paste that cites the evidence with its date, or null when the stored fields do not support one.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / open_opportunities / items / properties / quote
      Added value: +{
      +  "description": "The source's own words (dashes folded, clipped), or null when none is stored.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / open_opportunities / items / properties / quote_note
      Added value: +{
      +  "description": "When quote_status is not_stored, the plain sentence that says so. Null when a quote is stored.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / open_opportunities / items / properties / quote_status
      Added value: +{
      +  "description": "stored: quote holds the source's words. not_stored: no quote is stored for this lead.",
      +  "enum": [
      +    "stored",
      +    "not_stored"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / open_opportunities / items / properties / quote_text
      Added value: +{
      +  "description": "The quote delimited as a quote (\"The source says: ...\"), or null when none is stored.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / open_opportunities / items / properties / source_url
      Added value: +{
      +  "description": "The link the quote, or with no quote the lead's newest source, is on.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "account": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "domain": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "id": {
      +          "type": "string"
      +        },
      +        "name": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "name"
      +      ],
      +      "type": "object"
      +    },
      +    "as_of": {
      +      "format": "date-time",
      +      "type": "string"
      +    },
      +    "open_opportunities": {
      +      "items": {
      +        "additionalProperties": true,
      +        "description": "One lead.",
      +        "properties": {
      +          "account_id": {
      +            "type": "string"
      +          },
      +          "company": {
      +            "type": "string"
      +          },
      +          "domain": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "headline": {
      +            "type": "string"
      +          },
      +          "id": {
      +            "description": "The lead id (eop_...).",
      +            "type": "string"
      +          },
      +          "timing": {
      +            "type": "string"
      +          },
      +          "usually_means": {
      +            "description": "What this usually means for what the workspace sells. An interpretation, not confirmed intent.",
      +            "type": "string"
      +          },
      +          "usually_winds_down_by": {
      +            "format": "date",
      +            "type": "string"
      +          },
      +          "what_we_found": {
      +            "description": "The dated proof, newest first, each with a link to its source when there is one.",
      +            "items": {
      +              "additionalProperties": true,
      +              "properties": {
      +                "date": {
      +                  "description": "When the event happened, else when Intakra first saw it.",
      +                  "format": "date",
      +                  "type": "string"
      +                },
      +                "source": {
      +                  "type": "string"
      +                },
      +                "summary": {
      +                  "type": "string"
      +                },
      +                "url": {
      +                  "type": [
      +                    "string",
      +                    "null"
      +                  ]
      +                }
      +              },
      +              "required": [
      +                "date",
      +                "summary"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "company",
      +          "headline",
      +          "what_we_found"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "open_opportunities_truncated": {
      +      "type": "boolean"
      +    },
      +    "recent_findings": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "account_id": {
      +            "type": "string"
      +          },
      +          "company": {
      +            "type": "string"
      +          },
      +          "date": {
      +            "format": "date",
      +            "type": "string"
      +          },
      +          "domain": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "event_date": {
      +            "description": "When the public event happened, if known.",
      +            "format": "date",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "recorded_at": {
      +            "description": "When Intakra first recorded it.",
      +            "format": "date-time",
      +            "type": "string"
      +          },
      +          "source": {
      +            "type": "string"
      +          },
      +          "summary": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "recorded_at",
      +          "summary"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "recent_findings_limit": {
      +      "type": "integer"
      +    },
      +    "recent_findings_truncated": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "account",
      +    "open_opportunities",
      +    "recent_findings"
      +  ],
      +  "type": "object"
      +}
  3. Added
  4. Removed
  5. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the result is capped at roughly 12 dated findings with links plus open leads with dated proof, and it clarifies no fresh lookup is performed. Pagination and total-count behavior are still unstated.

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?

Three tight clauses: the trigger question first, then what comes back, then accepted input forms and the scope limit. No filler, and the most decision-relevant information is front-loaded.

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

Completeness5/5

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

For a one-parameter read tool with an output schema and full annotation coverage, the description supplies everything an agent needs: trigger, input forms, result shape and the 'saved records only' constraint. Return-value detail beyond this is unnecessary because an output schema exists.

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?

Schema coverage is 100% and the single parameter's own description already lists 'Domain, company name, or account id'. The description restates that and adds only a concrete example format ('acme.com'), which is marginally useful but not new meaning. Baseline 3 is appropriate when the schema carries the semantics.

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 (returns one tracked account) and immediately scopes it with a user-style trigger question. The phrase 'Saved records only, no new check' distinguishes it from record-creating siblings like add_accounts or request_accounts.

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 description gives a concrete when-to-use signal ('what do we know about acme.com?') and an implicit exclusion via 'saved records only, no new check', which tells the agent not to use this when new data must be fetched. It does not name the alternative tool explicitly, so the routing is clear but not fully spelled out.

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