Skip to main content
Glama

Intakra Buying Signals and Workspace

Read changes on a lead

get_project_updates
Read-onlyIdempotent

Use when the user asks what changed on one lead. Pass opportunity_id from list_opportunities or get_daily_brief (eop_...). Returns whether the lead is watched and up to 20 dated before/after changes with sources. Saved evidence only: no new research and no notification.

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": {
      "opportunity_id": "<opportunity_id>"
    },
    "name": "get_project_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
opportunity_idYesThe lead id (starts with eop_) from list_opportunities or get_daily_brief.

Output Schema

NameRequiredDescriptionDefault
activeYesWhether the lead is being watched.
changesYesUp to 20, newest first.
baselineNoThe saved snapshot changes are compared against, or null when never watched.
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / opportunity_id / description
      Added value: +"The lead id (starts with eop_) from list_opportunities or get_daily_brief."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "active": {
      +      "description": "Whether the lead is being watched.",
      +      "type": "boolean"
      +    },
      +    "baseline": {
      +      "description": "The saved snapshot changes are compared against, or null when never watched."
      +    },
      +    "changes": {
      +      "description": "Up to 20, newest first.",
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "after": {},
      +          "at": {
      +            "format": "date-time",
      +            "type": "string"
      +          },
      +          "before": {},
      +          "deliveries": {
      +            "items": {
      +              "additionalProperties": true,
      +              "properties": {
      +                "channel": {
      +                  "type": "string"
      +                },
      +                "status": {
      +                  "type": "string"
      +                }
      +              },
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "kinds": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "summary": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "summary",
      +          "at"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "checkedAt": {
      +      "format": "date-time",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "active",
      +    "changes"
      +  ],
      +  "type": "object"
      +}
  2. Added
  3. Removed
  4. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/closed-world, but the description adds behavior beyond them: watched status in the response, a cap of up to 20 dated before/after changes with sources, and the important constraint that no fresh research or notification occurs. The only minor gap is that it doesn't say what an empty result looks like for an unwatched lead.

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 short sentences, front-loaded with the usage trigger, then the parameter source, then the behavioral constraint. No filler and nothing a reader must dig for.

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?

With a single fully documented parameter, rich annotations, and an output schema covering return shape, the description supplies everything still needed: the trigger, the id origin, the scope limit, and the 'no new research' caveat.

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 schema already states the id comes from list_opportunities or get_daily_brief and starts with eop_; the description repeats essentially the same information. It adds no new syntax, format, or validation meaning, so the baseline 3 applies.

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 opens with a concrete verb+resource: 'what changed on one lead', and names the sibling source tools (list_opportunities, get_daily_brief). This separates it from get_account_changes (account-level) and get_daily_brief (portfolio-level) without needing the schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the exact trigger ('Use when the user asks what changed on one lead'), tells where the id comes from, and gives an explicit exclusion: 'Saved evidence only: no new research and no notification.' That covers when to use and when not to.

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