Skip to main content
Glama

Intakra Buying Signals and Workspace

Review changes on your account list

get_account_changes
Read-onlyIdempotent

Use for 'anything happening on my list?' or 'what changed at these companies this week?'. Returns findings recorded since a date (default seven days ago) for the tracked accounts, each with the event date, the date Intakra recorded it and a source link. Optional domains restrict the list. A finding can describe an older event recorded recently, and no findings is not proof of no activity. Saved records only.

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

Input Schema

NameRequiredDescriptionDefault
limitNoFindings to return, default 50. Narrow since or domains if truncated.
sinceNoStart date YYYY-MM-DD or ISO 8601 timestamp with timezone, not in the future. Default: seven days ago.
domainsNoOptional company domains to check against your tracked list, up to 200. Omit to use your tracked accounts.

Output Schema

NameRequiredDescriptionDefault
as_ofNo
sinceNo
changesYes
accountsNo
date_basisNo
coverage_noteNo
missing_domainsNoRequested domains that are not on the list.
accounts_scannedNo
changes_truncatedNo
account_scan_truncatedNo
matching_tracked_accountsNo
account_check_details_truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "account_check_details_truncated": {
      +      "type": "boolean"
      +    },
      +    "account_scan_truncated": {
      +      "type": "boolean"
      +    },
      +    "accounts": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "added_at": {
      +            "format": "date-time",
      +            "type": "string"
      +          },
      +          "check_age_days": {
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          },
      +          "check_status": {
      +            "enum": [
      +              "checks_recorded",
      +              "no_completed_check_recorded",
      +              "awaiting_checks"
      +            ],
      +            "type": "string"
      +          },
      +          "domain": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "last_successful_check_at": {
      +            "format": "date-time",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "name": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "name",
      +          "check_status"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "accounts_scanned": {
      +      "type": "integer"
      +    },
      +    "as_of": {
      +      "format": "date-time",
      +      "type": "string"
      +    },
      +    "changes": {
      +      "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"
      +    },
      +    "changes_truncated": {
      +      "type": "boolean"
      +    },
      +    "coverage_note": {
      +      "type": "string"
      +    },
      +    "date_basis": {
      +      "type": "string"
      +    },
      +    "matching_tracked_accounts": {
      +      "type": "integer"
      +    },
      +    "missing_domains": {
      +      "description": "Requested domains that are not on the list.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "since": {
      +      "format": "date-time",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "changes"
      +  ],
      +  "type": "object"
      +}
  2. Added
  3. Removed
  4. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (which already declare a safe, idempotent read), the description discloses genuine behavioral caveats: a finding may describe an older event recorded recently, an empty result is not proof of no activity, and only saved records are searched. These are exactly the interpretation traps an agent would otherwise fall into.

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?

Roughly four sentences, front-loaded with the use case, then behavior, then caveats. Dense but every clause carries information; no filler or repetition of the title.

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 values need not be spelled out, and the description still names the key fields (event date, recorded date, source link). For a three-optional-parameter read tool with full annotations, the only minor gap is guidance on what to do when the limit truncates results, which lives only 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?

Schema coverage is 100%, so the baseline is 3; the description only restates the default window and that domains optionally restrict the list. It adds no format or interaction detail (e.g., how domains interact with since or limit) beyond what the schema already says.

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?

"Returns findings recorded since a date ... for the tracked accounts" gives a specific verb and resource, and the parenthetical user phrasings sharpen the intent. It never explicitly contrasts itself with list_accounts or get_account, so the sibling differentiation is left implicit.

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 two quoted user intents ('anything happening on my list?', 'what changed at these companies this week?') give an agent a clear trigger condition. There are no explicit exclusions or named alternatives for cases where a different tool would be better.

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