Skip to main content
Glama

Bilg

by com.bilgai
OverviewDiscussionsAdmin

create_open_question

Record an open question under an epic. Open questions track unresolved decisions or unknowns that need follow-up. Provide either epicId (UUID) or epicKey (short key like BLG-E15).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
epicIdNo
askedToNoWho should answer it: "me", a person's name, the email shown for members without a name, or id, or null. Defaults to unaddressed (falls back to the epic owner).
epicKeyNo
questionYesThe open question — one or two sentences

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / askedTo
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Who should answer it: \"me\", a person's name, the email shown for members without a name, or id, or null. Defaults to unaddressed (falls back to the epic owner)."
+}
  2. First observed

TDQS

A3.9/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It says the tool 'records' an open question, but does not mention persistence, side effects, permissions, what happens if both or neither epic identifier is provided, or what the tool returns. This is thin for a write operation.

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 two sentences with no filler. The core action and purpose are front-loaded, followed immediately by the parameter-selection hint. Every sentence earns its place.

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?

The description covers the tool's purpose, the identifier alternatives, and the nature of the question parameter, so an agent can likely invoke it correctly. However, with no annotations and no output schema, it leaves important gaps: what happens when neither or both identifiers are supplied, and what the created open question record looks like.

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 only 50% because epicId and epicKey have no descriptions in the schema. The description compensates by stating that the two are alternatives, clarifying that epicId is a UUID and giving a concrete short-key example like 'BLG-E15'. This adds meaningful guidance beyond the schema.

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 object: 'Record an open question under an epic.' It then defines what open questions are ('unresolved decisions or unknowns that need follow-up'), which distinguishes this from sibling tools like create_decision and create_task without needing to inspect the schema.

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?

The description gives clear context for when an open question is appropriate and instructs the agent to attach it to an epic via either epicId or epicKey. It does not explicitly name alternatives or state when not to use this tool, so it stops short of the top tier.

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

All Bilg toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources