Skip to main content
Glama
EQIQs

@eqiqs/mcp-server

Official
by EQIQs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Add a note

add_note

Save a private note or check-in about a colleague directly on their EQIQs profile after one-on-ones, so important context is remembered for future interactions.

Instructions

Save a private note or check-in on one person in the user's workspace; it appears on their EQIQs profile. Use after 1:1s or when the user asks to remember something about someone. Costs 1 unit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYesNote text (up to 4,000 characters).
personYesWho the note is about. Accepts a profile id, an exact email, or a full name. If a name matches more than one person the tool asks which one instead of guessing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / note / description
      Added value: +"Note text (up to 4,000 characters)."
    • addedInput schema / properties / note / maxLength
      Added value: +4000
    • addedInput schema / properties / note / minLength
      Added value: +1
    • addedInput schema / properties / person / description
      Added value: +"Who the note is about. Accepts a profile id, an exact email, or a full name. If a name matches more than one person the tool asks which one instead of guessing."
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no useful annotation hints (all four hints are false/absent), the description carries the behavioral burden and does disclose meaningful traits: the note is private, it appears on the person's profile, and it 'Costs 1 unit.' It doesn't discuss reversibility or error behavior, but it covers the main side effects an agent needs.

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?

Three short sentences, each earning its place: action/outcome, use-case guidance, and cost. It is front-loaded with the core purpose and has no filler.

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 low-complexity two-parameter tool, the description covers purpose, when to use it, outcome, and cost. It lacks an explicit statement about confirmation/return value, but there is no output schema and the missing detail is minor.

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%, so the schema already fully documents both parameters. The description adds no parameter-specific detail beyond 'on one person,' which is already reflected in the schema's 'Who the note is about.' Baseline 3 is appropriate.

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?

The description names a specific action ('Save'), a specific resource ('a private note or check-in on one person'), and the key side effect ('appears on their EQIQs profile'). It is clear enough that an agent can separate it from list_notes and the other sibling tools, though it never explicitly names a sibling distinction.

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?

It explicitly tells when to use the tool: 'after 1:1s or when the user asks to remember something about someone.' It does not provide exclusions or alternative tool names, so it falls just short of full routing guidance.

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