ChartHop Search MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_peopleA | Search the 1Password/AgileBits employee directory (ChartHop) by name. Args: query: A name (or partial name) to look up. Returns:
A list of matching people, each with |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap. The tool's purpose is clearly defined as searching for people by name.
The tool name 'search_people' follows the standard verb_noun convention, is descriptive, and is internally consistent, even though it is the only tool.
The server is explicitly a search MCP, so a single tool dedicated to searching people is well-scoped and earns its place. The narrow purpose does not require additional tools.
The tool fully covers the stated purpose of searching the employee directory by name and returns relevant fields. No obvious gaps exist for this narrow domain.