Skip to main content
Glama

SignalRaven

by io.github.signalraven
OverviewDiscussionsAdmin

Run Person Intelligence

run_person_intelligence

Start a Person Intelligence snapshot for a person’s LinkedIn URL — a buyer read plus any signals from their recent activity. If a snapshot for this person already exists it is returned free (cached: true) however old it is, until you ask for a refresh. SPENDS CREDITS when no snapshot exists or when refresh is true and the existing snapshot is at least 7 days old. Returns immediately with a snapshot id and status; poll get_person_intelligence until status is "ready". For ongoing weekly checks of a person use monitor_person instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refreshNoAsk for a new snapshot instead of the existing one. A refresh is only possible once the existing snapshot is 7 days old (before that the same snapshot is returned with refreshAvailableAt) and it spends credits like a first run.
personUrlYesA LinkedIn profile URL, e.g. https://www.linkedin.com/in/someone.
sourceCompanyReportIdNoOptional Account Intelligence report id this person came from, to keep the lineage.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ctaNoPresent in sample mode: how to get live data.
dataYesThe result, or null when nothing matched.
modeYeslive: the caller's workspace. sample: illustrative data for accounts without an approved workspace.
noticeNoPresent in sample mode: explains that the data is illustrative.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / refresh
      Added value: +{
+  "description": "Ask for a new snapshot instead of the existing one. A refresh is only possible once the existing snapshot is 7 days old (before that the same snapshot is returned with refreshAvailableAt) and it spends credits like a first run.",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses credit consumption, the free-cached-return behavior, the 7-day refresh eligibility window, the asynchronous pattern (returns immediately with snapshot id + status, then poll), and that the cached result is returned 'however old it is'. Annotations only declare readOnly=false / destructive=false / openWorld=true, so this description carries substantial extra behavioral load.

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?

Front-loads the core action, then the cost/caching rule, then the async contract, then the sibling alternative — each sentence adds a distinct decision-relevant fact. No filler despite the density.

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?

An output schema exists, yet the description still gives the essential async contract (snapshot id + status, poll until ready), and it covers cost, caching, refresh eligibility, and the alternative tool. Nothing an agent needs to call this correctly is missing.

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 refresh, personUrl, and sourceCompanyReportId are already documented in the schema — including the 7-day refresh rule and refreshAvailableAt. The description adds little parameter-level meaning beyond what the schema states, 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?

States a specific verb+resource ('Start a Person Intelligence snapshot for a person's LinkedIn URL') and immediately scopes what the snapshot contains ('a buyer read plus any signals from their recent activity'). It is clearly distinguishable from get_person_intelligence (the poller) and monitor_person (the recurring checker), both named in the text.

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?

Explicitly says when the call is free (existing snapshot, cached: true) versus when it spends credits (no snapshot, or refresh=true on a snapshot at least 7 days old). It routes the agent to two alternatives by name: poll get_person_intelligence until status is 'ready', and use monitor_person for ongoing weekly checks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SignalRaven toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources