Skip to main content
Glama

classify_use_case

Read-only

Propose an EU AI Act risk tier for a new AI use case from a plain-language description, so compliance can review the classification before adding it to the inventory.

Instructions

Propose an AI Act risk tier for a new AI use case described in plain language.

ai_role: 'deployer' if the company uses a bought system, 'provider' if it built it. Uses Claude when an API key is configured, otherwise the keyword baseline. The result is a proposal that compliance must review before it enters the inventory.

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": {
      "description": "<description>"
    },
    "name": "classify_use_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
ai_roleNodeployer
descriptionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds two non-obvious traits: the model backend varies (Claude when an API key is configured, keyword baseline otherwise), so output quality is configuration-dependent, and the result is advisory rather than authoritative. It still does not describe determinism, latency, or how ambiguous cases are handled.

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?

Four short, front-loaded lines with no filler: purpose first, then parameter semantics, then runtime behavior, then the review caveat. Every sentence adds information.

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?

For a two-parameter tool with an output schema, the definition covers purpose, parameter meaning, backend variability, and the downstream review step. Minor gaps remain around input length or detail expectations and failure behavior.

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 0%, so the description must carry the parameter meaning and it largely does, explaining that ai_role is 'deployer' for using a bought system and 'provider' for having built it, and that description is plain-language case text. It does not cover the default behavior consequences or how much detail the description string should contain.

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 first sentence gives a specific verb and resource: propose an AI Act risk tier for a new use case described in plain language. That is clearly distinct from siblings like obligations_for_use_case or evidence_gaps, though the description never explicitly contrasts itself with them.

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?

Usage is implied by 'for a new AI use case,' and the closing line establishes that the output is a proposal needing compliance review before entering the inventory. There is no explicit when-not-to-use guidance or reference to the sibling tools that consume the result.

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