Skip to main content
Glama
Sign In
Hermai MCP

Hermai MCP

Official
by hermai-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Classify a browser workflow

classify_browser_workflow
Read-onlyIdempotent

Identifies whether a described workflow uses direct API, hidden endpoint, browser-only, or requires owner authentication.

Instructions

Classify a prose workflow as direct API, hidden endpoint, browser-only, or needs owner/auth. Read-only and local.

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": {
      "prose": "<prose>"
    },
    "name": "classify_browser_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
proseYesPost, issue, or user request describing the workflow.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.2/5.0
Behavior5/5

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

Description adds 'Read-only and local' beyond annotations (readOnlyHint, idempotentHint), providing valuable context about mutability and scope. No contradictions.

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?

One concise sentence that front-loads the action and includes all essential information with no superfluous words.

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?

Given the simple input (one string) and no output schema, the description adequately explains the classification categories and behavioral traits, though it does not specify the return format explicitly.

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 single parameter 'prose' is fully described in the schema (100% coverage). The description adds a list of example sources but does not significantly enhance meaning 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 clearly states the verb 'classify' and the resource 'prose workflow' and lists the four possible output categories, distinguishing it from sibling tools which are schema-related.

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?

No explicit guidance on when to use this tool versus alternatives, but the specific task (classifying workflows) and sibling tools (schema lookups) make usage context clear by implication.

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