Skip to main content
Glama
Sign In

AgentBIT

by app.agentbit
OverviewDiscussionsAdmin

Company Brief (executive intelligence)

agentbit.company_brief
Read-onlyIdempotent

One-call executive brief on a company: aggregates enrichment + news + website + risk, then an LLM distills it into overview, products, developments, risks, opportunities. Pay-per-call via x402 (USDC, Base).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "agentbit.company_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoCompany domain (e.g. "stripe.com"). Provide this or company_name.
_paymentNoOptional base64 x402 PAYMENT-SIGNATURE payload. Omit to receive payment requirements.
company_nameNoCompany name. Provide this or domain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructiveness. The description adds meaningful behavioral context beyond those: it reveals the aggregation + LLM distillation flow and 'Pay-per-call via x402 (USDC, Base)', which is important operational cost/payment information an agent needs before invoking.

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?

The description is a single compact sentence with the purpose front-loaded ('One-call executive brief') and no filler. Every clause carries information: the aggregated sources, the LLM distillation, the output sections, and the payment model.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by naming the exact output sections delivered. It also covers the payment mechanism and the breadth of data sources, which is enough for an agent to understand the call's scope and cost. The main omissions are explicit routing around sibling enrichment/research tools, which is more of a usage-guideline gap.

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?

The input schema already documents all three parameters with 100% coverage, including the 'Provide this or company_name' relationship and the _payment behavior. The description adds no parameter-level meaning beyond the general notion of a 'company', so it earns the baseline score for high schema coverage.

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 opens with 'One-call executive brief on a company' and enumerates the pipeline ('aggregates enrichment + news + website + risk') and output sections ('overview, products, developments, risks, opportunities'). This clearly states what the tool does, but it does not explicitly name or contrast sibling tools such as company_enrich or company_research.

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?

The phrase 'One-call' and the aggregated-source list imply this is the holistic, quick-brief option, giving the agent a reasonable sense of when to use it. However, there is no explicit when-to-use, when-not-to-use, or alternative-tool guidance, so usage remains mostly implied rather than stated.

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

All AgentBIT 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