Skip to main content
Glama

SignalRaven

by io.github.signalraven
OverviewDiscussionsAdmin

Run Account Intelligence

run_account_intelligence

Start an Account Intelligence report for a company LinkedIn URL — firmographics, an ICP verdict, and the buying committee. If a report for this company already exists it is returned free (cached: true) however old it is, until you ask for a refresh. SPENDS CREDITS when no report exists or when refresh is true and the existing report is at least 7 days old. Returns immediately with a report id and status; poll get_account_intelligence until status is "ready".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refreshNoAsk for a new report instead of the existing one. A refresh is only possible once the existing report is 7 days old (before that the same report is returned with refreshAvailableAt) and it spends credits like a first run.
companyUrlYesA LinkedIn company URL, e.g. https://www.linkedin.com/company/acme.

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 report instead of the existing one. A refresh is only possible once the existing report is 7 days old (before that the same report is returned with refreshAvailableAt) and it spends credits like a first run.",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), and the description adds substantial context beyond them: credit consumption triggers, cache-first behavior regardless of age, the 7-day refresh floor with refreshAvailableAt, and the asynchronous 'returns immediately with a report id and status' contract. That is exactly the non-obvious operational behavior an agent needs.

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?

Four tight sentences, front-loaded with the action and its artifact, then cost, then the async contract. No filler; the caps on SPENDS CREDITS correctly emphasize the highest-stakes clause.

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 an output schema present the description needn't explain return fields, yet it still covers the polling prerequisite and status transition to 'ready'. For a credit-spending async job with a cache layer, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are documented in structured form. The description nonetheless adds meaning to refresh beyond the schema: the 7-day eligibility window, the refreshAvailableAt fallback, and that it 'spends credits like a first run'. It adds little for companyUrl beyond what the schema already says.

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 specific verb and resource — 'Start an Account Intelligence report for a company LinkedIn URL' — and enumerates the deliverable content (firmographics, ICP verdict, buying committee). It is immediately distinguishable from siblings like get_account_intelligence (poll) and run_person_intelligence (person scope).

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 states when a cached report is returned free, when credits are spent (no report exists, or refresh=true on a report at least 7 days old), and routes the agent to get_account_intelligence for polling. This is a complete when/when-not/alternative map with the credit cost condition called out in caps.

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