Skip to main content
Glama
forbiz-mcp

forbiz-mcp

Record a signal check

forbiz_check_signal

Record the result of checking for an expected signal on an action, including source, period, and reason for cannot-check.

Instructions

Record that you looked for the expected signal (POST /actions/{id}/signal-checks). not_found_in_source REQUIRES source and period: it says where you looked and when, never that a third party did not answer. found closes nothing; link the signal with forbiz_record_signal. cannot_check REQUIRES reason.

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": {
      "id": "<id>",
      "result": "<result>"
    },
    "name": "forbiz_check_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAction id
noteNo
periodNoThe time window you checked
reasonNo
resultYes
sourceNoWhere you looked, e.g. { kind: 'email_thread', detail: 'Re: quote' }
looked_forNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations cover the safety profile (destructiveHint=false, openWorldHint=true, readOnlyHint=false = a mutation with no destructive risk). The description adds non-obvious behavioral facts beyond that: that recording 'found' closes nothing, and the specific field obligations attached to each result value. These are meaningful, non-schema behavioral disclosures.

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?

Dense, front-loaded sentences with no filler; the behavior for each result state is stated tersely. The parenthetical endpoint is slightly redundant since the tool name already implies the resource, but overall it wastes little.

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?

For a mutating tool with 7 params, 43% schema coverage, nested objects, and no output schema, the description covers the result-dependent behaviors and the key alternative well but omits what note and looked_for are for and how they interact with the result states. Adequate but with visible gaps.

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 only 43% across 7 params, so the description is required to compensate. It does explain the conditional semantics of result values (not_found_in_source needs source+period; cannot_check needs reason) and the meaning of source/period ('where you looked and when'), but leaves note, looked_for, and id semantics unaddressed.

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?

States a specific verb+resource ('Record that you looked for the expected signal') and anchors it to the endpoint POST /actions/{id}/signal-checks, so the agent knows exactly what action is taken. It names forbiz_record_signal as the tool for linking a found signal, giving partial sibling differentiation, though it never addresses the closely-related forbiz_close_without_signal.

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?

Gives concrete conditional guidance: not_found_in_source requires source+period, cannot_check requires reason, and 'found closes nothing; link the signal with forbiz_record_signal' explicitly routes a finding to the alternative tool. It stops short of full when-to-use/when-not coverage (e.g. no boundaries against close_without_signal), but the routing to a sibling is genuinely present.

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