Skip to main content
Glama
EQIQs

@eqiqs/mcp-server

Official
by EQIQs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Score a team

score_team
Read-onlyIdempotent

Score a group of 3+ people in one call: get team cohesion score, weakest shared dimension, most isolated and best-connected members, pairings to watch, and role gaps.

Instructions

Score a whole group in one call: every pairing is rolled up into a team cohesion score (visual card), the weakest shared dimension, the best-connected person, who is most isolated, pairings to watch (<55) and anchor pairings (75+), and the role mix with what is missing. Use instead of looping score_compatibility for 3+ people. Decision-support only. Read-only; costs 2 units.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelNoOptional group name echoed in the summary.
contextNoRelationship context that sets framework weighting. 'business' (default) is work-safe and withholds personal-life signals (love language, attachment style, date of birth); the other contexts include them.business
membersNoProfile ids or full names of the people in the group (2-12). Omit when using department.
departmentNoUse everyone tagged with this department instead of naming members. Exact match first; refuses and asks for names if more than 12 people match or the name spans several departments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.1.1
    • addedInput schema / properties / context / default
      Added value: +"business"
    • addedInput schema / properties / context / description
      Added value: +"Relationship context that sets framework weighting. 'business' (default) is work-safe and withholds personal-life signals (love language, attachment style, date of birth); the other contexts include them."
    • changedInput schema / properties / department / description
      Previous value: -"Score everyone in this department instead of naming members."New value: +"Use everyone tagged with this department instead of naming members. Exact match first; refuses and asks for names if more than 12 people match or the name spans several departments."
    • addedInput schema / properties / department / maxLength
      Added value: +100
    • addedInput schema / properties / label / description
      Added value: +"Optional group name echoed in the summary."
    • addedInput schema / properties / label / maxLength
      Added value: +80
    • changedInput schema / properties / members / description
      Previous value: -"Profile ids or names (2-12)."New value: +"Profile ids or full names of the people in the group (2-12). Omit when using department."
    • addedInput schema / properties / members / maxItems
      Added value: +12
    • addedInput schema / properties / members / minItems
      Added value: +2
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint=false), the description discloses that the call costs 2 units, is decision-support only, and rolls up every pairing rather than returning per-pair details. It also mentions the 'visual card' output, which is a behavioral trait not inferable from the schema or annotations.

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 well-structured: it front-loads the core purpose, then lists the output contents, then gives usage guidance and constraints. Every sentence contributes value, and the length is proportional to the tool's complexity.

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?

With no output schema, the description takes responsibility for explaining return values, and it enumerates them thoroughly: cohesion score, weakest dimension, best-connected person, most isolated person, watch/anchor pairings, and role mix. It also covers cost, read-only behavior, and the alternative tool, making it complete for an agent to invoke correctly.

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 description coverage is 100%, so all parameters are already documented with their meanings. The tool-level description does not add meaningful parameter semantics beyond what the schema provides, but it also does not need to compensate for gaps.

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 opens with a specific verb and resource: 'Score a whole group in one call,' and clearly differentiates itself from score_compatibility by aggregating all pairings into one team-level result. It also lists the concrete outputs (cohesion score, weakest dimension, best-connected person, etc.), leaving no ambiguity about what the tool does.

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?

It explicitly states when to use this tool: 'Use instead of looping score_compatibility for 3+ people.' This directly names the alternative and the threshold, making the selection decision unambiguous. The 'Decision-support only' qualifier further frames appropriate usage.

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