Skip to main content
Glama

Intakra Buying Signals and Workspace

Prepare an evidence-labeled why-now review

prepare_why_now_review
Read-only

Turn caller-supplied fit criteria and business signals into reviewable why-now and fit guidance. Every fact remains labeled caller-supplied and unverified. The tool does not research, infer budget or buyer intent as fact, draft outreach, access private data, persist input, or take action.

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>",
      "vendor": "<vendor>",
      "fitCriteria": "<fitCriteria>",
      "signals": "<signals>"
    },
    "name": "prepare_why_now_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendorYes
accountYes
signalsYes
asOfDateNoOptional date for reproducible recency scoring. Defaults to the current California date.
fitCriteriaYes

Output Schema

NameRequiredDescriptionDefault
statusYes
whyNowYes
headlineYes
accountNameYes
dispositionYes
fitGuidanceYes
evidenceGapsYes
supportedFactsYes
prohibitedActionsYes
requiresHumanReviewYes
questionsForReviewerYes
sourceVerificationPerformedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety and scope are partly covered. The description goes beyond them by disclosing that input is not persisted, no private data is accessed, no action is taken, and every fact stays labeled caller-supplied and unverified—genuinely useful behavioral context for a review artifact.

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?

Three short sentences with the core purpose front-loaded and the constraint list kept compact. No filler or repetition; the caveats are dense but each one carries distinct information.

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

Completeness3/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 no explanation, and the labeling/no-side-effect guarantees are well covered. What is missing is enough parameter-level and selection detail for a complex tool with nested objects, five parameters, and only 20% schema coverage—adequate but with clear gaps.

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

Parameters2/5

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

Schema description coverage is only 20%, so the description carries much of the burden for five parameters including nested vendor, account, signals, and fitCriteria objects. It adds essentially nothing parameter-specific beyond the general 'fit criteria and business signals' phrase—no mention of asOfDate, confidence, observedAt, or the assessment enum—so it does not compensate for the coverage gap.

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?

The description states a specific verb and resource: 'Turn caller-supplied fit criteria and business signals into reviewable why-now and fit guidance.' That is far more concrete than the title alone. It does not, however, name or contrast with the sibling score_buying_signal_evidence, so an agent must infer the boundary between producing guidance and scoring evidence.

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

Usage Guidelines3/5

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

Usage is implied through exclusions ('does not research, infer budget or buyer intent as fact, draft outreach, access private data, persist input, or take action'), which tells the agent what situations this tool is not for. There is no explicit when-to-use statement and no routing to the sibling tool for scoring, so the selection guidance remains inferential.

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