Skip to main content
Glama
Sign In
ews-outlook-mcp

ews-outlook-mcp

by devsergioherrera
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Buscar contacto en la libreta de la empresa (GAL)

ews_resolve_contact
Read-only

Searches the corporate Outlook address book by partial name and returns matching email addresses. Use it to confirm the correct email before inviting someone to a meeting.

Instructions

Busca por nombre parcial en la Global Address List de Integral de Empaques (la libreta corporativa de Outlook) y devuelve coincidencias con su correo. Úsalo antes de invitar a alguien por nombre a una reunión, para confirmar el correo correcto.

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": {
      "nombre": "<nombre>"
    },
    "name": "ews_resolve_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
nombreYesNombre o parte del nombre a buscar, ej. 'Felipe Castillo'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is known. The description adds behavioral context beyond that: it performs partial-name matching, returns email addresses, and is scoped to the company's GAL. It doesn't detail result limits or error handling, but the added context is meaningful.

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?

Two concise sentences: the first directly states the tool's function, the second provides usage context. No redundant detail, and the key information is front-loaded.

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?

For a single-parameter, read-only search tool with no output schema, the description adequately covers what it does, what it returns (matches with email), and when to use it. The annotations handle the safety profile, making this complete.

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% with the 'nombre' parameter description including an example ('ej. Felipe Castillo'). The description merely restates that the search is by partial name, adding no new parameter-level meaning, so the baseline of 3 applies.

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 searches by partial name in the Global Address List and returns matches with their email, specifying the exact resource ('Global Address List de Integral de Empaques') and the result. This distinguishes it from sibling tools like ews_search_inbox or ews_add_attendee.

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 provides explicit when-to-use guidance: 'Úsalo antes de invitar a alguien por nombre a una reunión, para confirmar el correo correcto.' It lacks explicit when-not-to-use or alternative tool mentions, but the context is clear enough for a single-purpose tool.

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