Skip to main content
Glama

EMOS Advisor

Ask the EMOS Advisor

ask_advisor
Read-only

Answers a question about running a senior executive job search with EMOS: positioning, the four areas, how the program works, and where to start. Pass the person's question in their own words. Keep every link's destination exactly as given, never state a price, plan or credit (a cost question gets the consultation link), and never describe EMOS as guaranteeing a role or a placement. Never review a specific severance, release, separation or employment agreement, its terms, the person's legal rights or any legal deadline, and never search for them: that is for the person's employment attorney. When the person wants to reach a hiring manager or another decision-maker, the EMOS way in is a warm introduction first, through someone who knows them; add no outreach steps of your own and draft no message, email or call script for them.

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": {
      "question": "<question>"
    },
    "name": "ask_advisor"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is settled; the description adds genuine policy context beyond that — preserve link destinations verbatim, never state a price, plan or credit (cost questions get the consultation link), never promise a role or placement, and add no outreach steps. What is missing is any hint of the response shape (answer plus curated links), which is implied only indirectly.

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?

Purpose is front-loaded in the first sentence, followed by input guidance, then content constraints and exclusion zones in a tight sequence. The enumeration of forbidden behaviors is dense but each clause prevents a distinct failure mode, and no sentence merely restates the name or annotations.

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 single-parameter, read-only Q&A tool with no output schema, the description covers purpose, input formulation and the main behavioral guardrails (pricing, guarantees, legal topics, outreach). Nothing critical is absent, though a brief note on what a response looks like — a direct answer with program links — would close the remaining gap.

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 description coverage is 0%, so the description must carry the parameter, and it does: the single 'question' argument should be the person's question verbatim, in their own words. That tells the agent how to formulate the input rather than rewriting or splitting it, which the bare string/maxLength=2000 schema does not convey, though it does not mention the length limit.

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?

States a specific verb and resource — answering questions about running a senior executive job search with EMOS — and enumerates covered topics (positioning, the four areas, how the program works, where to start). It does not name or differentiate from the siblings how_emos_works and next_step, and 'how the program works' overlaps with how_emos_works, so an agent must infer the boundary rather than read it.

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?

Gives clear positive usage ('Pass the person's question in their own words') and strong exclusions: no severance/release/legal-agreement review or search, and no outreach drafting. The routing for those exclusions points to an employment attorney rather than to a sibling tool, so the when-to-use-this-vs-how_emos_works/next_step decision is left implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources