LittleSis 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_entityB | Get detailed information about a specific entity (person or organization) from LittleSis by ID |
| get_entitiesB | Get information about multiple entities at once (up to 300 entities per request) |
| search_entitiesC | Search for entities by name. Results are ranked by number of relationships. |
| get_entity_extensionsC | Get the types/extensions associated with an entity (Person, Organization, Business, etc.) |
| get_entity_relationshipsC | Get all relationships this entity has with other entities |
| get_entity_connectionsC | Get other entities that this entity has relationships with |
| get_entity_listsC | Get the lists that an entity appears on (e.g., Fortune 1000, lobbying lists) |
| get_relationshipC | Get detailed information about a specific relationship between two entities |
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 8 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are well-segmented: get_entity for single entity details, get_entities for batch retrieval, get_entity_connections for related entities, get_entity_extensions for entity types, get_entity_lists for list membership, get_entity_relationships for relationship details, get_relationship for specific relationship info, and search_entities for name-based searching. There is no overlap in functionality.
All tools follow a consistent verb_noun pattern with 'get_' or 'search_' prefixes and snake_case naming. The naming is highly predictable: get_entity, get_entities, get_entity_connections, get_entity_extensions, get_entity_lists, get_entity_relationships, get_relationship, and search_entities. There are no deviations or mixed conventions.
The 8 tools are well-scoped for the LittleSis domain, which focuses on entity and relationship data. Each tool earns its place by covering distinct aspects like entity retrieval, relationship details, extensions, lists, and searching. This count is typical for a data-focused API and avoids being too thin or heavy.
The tool set provides comprehensive coverage for querying entities and relationships, including CRUD-like operations for reading (get, search) and exploring connections. Minor gaps exist, such as no explicit tools for creating, updating, or deleting data, but these are likely intentional for a read-only API, and agents can work around this with the available tools for full query workflows.