Skip to main content
Glama

business_invention_disclosure

Read-onlyIdempotent

Invention disclosure worksheet

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": {
      "title": "<title>",
      "inventor": "<inventor>",
      "problem": "<problem>",
      "solution": "<solution>"
    },
    "name": "business_invention_disclosure"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDay of the disclosure, any readable form (free text), for example 17 Oct 2026.
titleYesName of the invention, for example Self-cleaning water bottle.
problemYesThe problem it solves, in plain words.
inventorYesInventor's full name, for example: Jane Smith.
solutionYesHow the invention solves it, in plain words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / date / description
      Added value: +"Day of the disclosure, any readable form (free text), for example 17 Oct 2026."
    • addedInput schema / properties / inventor / description
      Added value: +"Inventor's full name, for example: Jane Smith."
    • addedInput schema / properties / problem / description
      Added value: +"The problem it solves, in plain words."
    • addedInput schema / properties / solution / description
      Added value: +"How the invention solves it, in plain words."
    • addedInput schema / properties / title / description
      Added value: +"Name of the invention, for example Self-cleaning water bottle."
  2. Changed4 schema fields changed
    • addedInput schema / properties / inventor / minLength
      Added value: +1
    • addedInput schema / properties / problem / minLength
      Added value: +1
    • addedInput schema / properties / solution / minLength
      Added value: +1
    • addedInput schema / properties / title / minLength
      Added value: +1
  3. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context of its own: it does not say what is produced (a document, a file, structured text), whether the worksheet is stored or returned, or whether the required fields are merely echoed back.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is certainly short, but brevity here comes from under-specification rather than economy; three words carry no leading verb or scope statement. There is no waste, but there is also almost no content to structure.

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

Completeness2/5

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

For a five-parameter tool with four required fields and no output schema, the description should at minimum say what the caller receives back and in what form. Neither the return value nor the generation behavior is described, leaving a real gap that the annotations cannot fill.

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 description coverage is 100%, with each of the five fields carrying an example and plain-language explanation, so the schema does the heavy lifting and the baseline is 3. The description contributes nothing additional about the parameters, but nothing is lost given the rich schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is the noun phrase "Invention disclosure worksheet," which essentially restates the tool name and title rather than stating a verb+resource action. An agent can guess it produces some kind of disclosure form, but nothing says whether it generates, validates, or fills a worksheet, and it does nothing to distinguish itself from siblings like business_nda_draft or business_contract_pack.

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?

There is no when-to-use, when-not-to-use, or alternative-tool guidance anywhere in the description. The agent must infer from the name alone that this is for documenting a new invention rather than, say, filing a patent or drafting an NDA.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources