Skip to main content
Glama
Sign In
Email MCP Server

Email MCP Server

by 123jixinyu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_hooks_config

Read-only

Retrieve the active AI hooks configuration, including preset, rules, and custom instructions, to understand current email automation settings.

Instructions

Get the current AI hooks configuration including preset, rules, and custom instructions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_hooks_config"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds context about the returned content (preset, rules, custom instructions) but does not disclose any other behavioral traits such as caching, authentication requirements, or error conditions.

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, concise sentence that front-loads the action ('Get') and resource ('AI hooks configuration'). Every word contributes meaning, with no redundant or vague phrasing.

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 simple zero-parameter getter with strong annotations, the description is mostly complete. It names the key components of the configuration, though it does not describe the exact return structure or potential edge cases. Given the low complexity, this is sufficient.

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?

With zero parameters, the schema fully defines the input and the description naturally adds no parameter-level detail. The baseline of 4 for no-parameter tools applies, and the description's mention of return contents partially compensates for the lack of a response 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 tool gets the current AI hooks configuration, listing specific components (preset, rules, custom instructions). The verb 'Get' is specific and the resource is well-defined, distinguishing it from related tools like list_presets.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention why one would choose get_hooks_config over list_presets or other configuration-related tools, leaving the decision entirely to the agent.

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