Skip to main content
Glama
Sign In
WBSO MCP Server

WBSO MCP Server

by rubenmaas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

log_research

Record research time and findings in WBSO documentation by logging hours, technical uncertainties, and discovered outcomes to support R&D tax credit tracking.

Instructions

Log a research entry to WBSO 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": {
      "log_name": "<log_name>",
      "hours": "<hours>",
      "technical_uncertainty": "<technical_uncertainty>",
      "findings": "<findings>"
    },
    "name": "log_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursYesHours spent
approachNoHow you investigated this
findingsYesWhat you discovered
jira_refNoJira issue reference
log_nameYesName of the research log
conclusionNoDecisions made or next steps
technical_uncertaintyYesThe technical question being investigated

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the action 'log' without disclosing side effects (e.g., writes to WBSO documentation), permission requirements, or any return/error behavior. This is minimal disclosure 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 a single sentence with no fluff, front-loading the key action and target. It is appropriately concise for the simple operation it describes.

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 tool is a straightforward logging operation, and the schema covers parameter details. However, the description lacks context about what WBSO documentation is, what constitutes a research entry, and how this relates to sibling tools like log_development. It is adequate but minimal.

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 describes all 7 parameters with 100% coverage. The description itself adds no param-specific meaning beyond what the schema already provides. The baseline of 3 applies since the schema handles the heavy lifting.

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 action 'log' and the resource 'research entry to WBSO documentation'. It implicitly distinguishes from sibling tools like log_development by specifying 'research', but does not explicitly call out the differentiation.

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 such as log_development or log_time. It does not mention any prerequisites, exclusions, or context for when logging a research entry is appropriate.

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