Skip to main content
Glama
Sign In
Hermoso

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Read a tool's full instructions

get_instructions
Read-onlyIdempotent

Fetch complete instructions for a Hermoso tool or the paid-calls topic before calling when short descriptions omit required rules.

Instructions

Return the FULL instructions for a Hermoso tool whose description ends "Full rules: get_instructions(…)", or for any tool by name, or topic "paid-calls" for get_cost, expected_credits, idempotency_key, revision and context. Read it before a call that depends on rules the short description leaves out. Free.

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": {
      "topic": "<topic>"
    },
    "name": "get_instructions"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesa tool name (e.g. make_thumbnail) or "paid-calls"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.532

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description does not need to restate safety; instead it adds 'Free', which discloses that the lookup consumes no credits, a fact not present in structured fields. It also implies the return value is the full instruction text, which is meaningful since no output schema exists.

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

Conciseness4/5

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

Two sentences, front-loaded with the verb and resource, with no filler; the trigger condition is placed after the what-is-it statement. The long first sentence packs several clauses together, which makes it slightly dense but not wasteful.

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

Completeness5/5

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

This is a one-parameter read tool with full schema coverage and annotations covering its safety profile, so the description only needed to explain the lookup target and when to reach for it, and it does both. Nothing an agent needs to call it correctly is missing.

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 coverage is 100% and the schema already says topic is 'a tool name (e.g. make_thumbnail) or "paid-calls"', so the description largely repeats it. The one genuine addition is enumerating what the 'paid-calls' topic covers (get_cost, expected_credits, idempotency_key, revision, context), which slightly expands on the schema but not enough to exceed the baseline.

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 opens with a specific verb and resource ('Return the FULL instructions for a Hermoso tool') and scopes the input to either a tool name or the special topic 'paid-calls'. It is clearly a meta/reference lookup rather than an execution tool, which separates it from siblings like call_tool or read_doc, though the unexplained product name 'Hermoso' adds slight noise.

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?

It gives an explicit trigger condition ('Read it before a call that depends on rules the short description leaves out') and even tells you how to spot that condition in other tool descriptions ('ends "Full rules: get_instructions(…)"'). It stops short of stating when NOT to bother, but the positive guidance is concrete and actionable.

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