Biel AI

biel_ai

Ask Biel.ai's AI questions about code, SDKs, and documentation. Get answers grounded in your product documentation.

Instructions

Query Biel.ai's specialized AI about code, SDKs and documentation

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": {
      "message": "<message>"
    },
    "name": "biel_ai"
  }
}

Input Schema

Name	Required	Description
`domain`	No	Domain URL. Required only if 'Allowed domains' is enabled in project settings.
`api_key`	No	API key for authentication (optional)
`message`	Yes	Your question about code, SDK or documentation
`metadata`	No	Metadata to tag the conversation source (optional)
`chat_uuid`	No	Chat UUID to continue conversation (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 12, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only says 'Query,' which implies a read-like operation, but does not disclose that this may send data to an external AI service, require authentication (though params suggest an API key), or have any side effects. Important behavioral context such as network calls, data privacy, or response handling is omitted.

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?

The description is a single, focused sentence that front-loads the action and purpose without any filler. It is concise and well-structured, though it could potentially add a hint about response format or usage context without becoming verbose. Still, it earns its place and is not over-specified.

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?

While the input schema comprehensively documents all parameters, the description lacks guidance on what the AI returns (no output schema) and does not explain the broader context of how the tool should be invoked (e.g., optional domain, API key, chat continuation). For a query tool with 5 parameters, this is adequately functional but not rich enough to fully guide an agent without further clues.

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 schema description coverage is 100%, with all five parameters individually described in the input schema. The tool description itself adds no parameter-specific semantics beyond what the schema already provides. As a result, a baseline score of 3 is appropriate; the schema does the heavy lifting, and the description does not enhance understanding of parameters.

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 clearly states the tool's function: querying Biel.ai's specialized AI about code, SDKs, and documentation. It uses a specific verb ('Query') and resource ('Biel.ai's specialized AI'), making the purpose distinct even without sibling tools to differentiate from. However, the term 'specialized AI' is somewhat generic, which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, and no exclusion criteria. Since there are no sibling tools or context signals, the agent is left without explicit usage conditions or scenarios where this tool should or shouldn't be used. This is a clear gap in usage guidance.

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

Deploy Server

Other Tools

biel_aiC