Skip to main content
Glama
Sign In
ReactUse

ReactUse

by childrentime
OverviewSchemaSourceRelated ServersDiscussionsAdmin

Get hook details

get_hook
Read-onlyIdempotent

Retrieve complete documentation for any @reactuses/core React hook, including usage examples and API tables, to implement the correct hook in your code.

Instructions

Fetch full documentation (description, usage example, API table) for a specific @reactuses/core React hook by name.

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": {
      "hook_name": "<hook_name>"
    },
    "name": "get_hook"
  }
}

Input Schema

NameRequiredDescriptionDefault
hook_nameYesHook name, e.g. "useToggle", "useClipboard". Case-insensitive.

Output Schema

NameRequiredDescriptionDefault
apiYesAuto-generated API table (arguments, returns)
urlYes
bodyYesMarkdown body of the hook documentation (usage, examples, notes)
nameYes
categoryYes
descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv6.3.3

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds value by specifying the exact content returned (description, usage example, API table), which goes beyond the annotations. 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?

The description is a single, well-structured sentence that conveys the complete purpose. No extraneous information; every word earns its place.

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?

Given the low complexity (1 parameter), presence of output schema, and clear annotations, the description is fully adequate. It tells the agent what the tool does and what it returns, without needing further elaboration.

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?

Only one parameter (hook_name) with schema description coverage at 100%. The description does not add extra meaning beyond what the schema provides; it simply restates the purpose. Baseline of 3 is appropriate.

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 ('Fetch') and resource ('full documentation for a specific @reactuses/core React hook by name'). It distinguishes from sibling tools (list_hooks, search_hooks) by specifying that it targets a single hook by name and returns detailed documentation.

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?

The description implies use when one needs detailed docs for a specific hook. It does not explicitly state when not to use or compare with siblings, but the context is clear and the sibling list is provided in the context signals.

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