Skip to main content
Glama

EMOS Advisor

How EMOS works

how_emos_works
Read-onlyIdempotent

What Executive Momentum OS is, the four areas it works on, and who it is for. Use when someone asks what EMOS is or how it works. 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

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": "how_emos_works"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds substantive behavioral constraints beyond that: links must be reproduced verbatim, no prices/plans/credits, no guarantees of placement, no drafting of outreach messages, and warm introduction only as the route to a decision-maker. It stops short of saying what the response looks like, but the constraint disclosure is unusually rich for a read-only explainer.

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

Conciseness3/5

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

Purpose and trigger are front-loaded, which is good, but the description then piles on policy rules (legal review exclusions, outreach drafting prohibitions, link fidelity) that read like a shared guardrail block rather than content specific to an 'what is EMOS' explainer. Every sentence carries instruction value, yet the density dilutes the core selection signal for a zero-argument overview tool.

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?

With no parameters, no output schema, and annotations already covering the read-only/idempotent profile, the remaining burden is purpose, trigger and behavioral guardrails — all present. The only gap is a brief note on what the agent gets back (e.g., overview text with fixed links), which would round it out.

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?

The input schema is an empty object with zero parameters, so there is no parameter semantics to document. Baseline 4 applies; the description adds nothing misleading about inputs.

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 definition opens with a specific verb-and-resource statement: what EMOS is, the four areas it works on, and who it is for. Combined with 'Use when someone asks what EMOS is or how it works,' an agent can immediately tell this is the explanatory/overview tool rather than a workflow or advisory tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit positive trigger ('someone asks what EMOS is or how it works') plus concrete exclusions: cost questions route to the consultation link, legal/severance questions route to the person's employment attorney and must not even be searched. These are real when-to-use and when-not-to-use rules, not implied ones.

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