Skip to main content
Glama
code-rabi

LittleSis MCP

by code-rabi

get_entity_lists

Retrieve lists containing a specific entity, such as Fortune 1000 or lobbying registries, to track corporate affiliations and influence networks.

Instructions

Get the lists that an entity appears on (e.g., Fortune 1000, lobbying lists)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe entity ID

Implementation Reference

  • Handler function that executes the 'get_entity_lists' tool: calls LittleSisApi.getEntityLists with the provided entity ID, formats the JSON response, and handles errors.
    export async function handleGetEntityLists(args: any) {
      try {
        const result = await LittleSisApi.getEntityLists(args.id);
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2)
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error fetching entity lists: ${error instanceof Error ? error.message : 'Unknown error'}`
            }
          ],
          isError: true
        };
      }
  • Tool schema definition for 'get_entity_lists', specifying input as an object with required 'id' number property.
    export const getEntityListsTool: Tool = {
      name: 'get_entity_lists',
      description: 'Get the lists that an entity appears on (e.g., Fortune 1000, lobbying lists)',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'number',
            description: 'The entity ID'
          }
        },
        required: ['id']
      }
    };
  • src/index.ts:72-81 (registration)
    Registration of tool handlers in the mapping object used by CallToolRequestSchema handler to dispatch 'get_entity_lists' to handleGetEntityLists.
    const toolHandlers = {
      get_entity: handleGetEntity,
      get_entities: handleGetEntities,
      search_entities: handleSearchEntities,
      get_entity_extensions: handleGetEntityExtensions,
      get_entity_relationships: handleGetEntityRelationships,
      get_entity_connections: handleGetEntityConnections,
      get_entity_lists: handleGetEntityLists,
      get_relationship: handleGetRelationship,
    };
  • src/index.ts:58-69 (registration)
    Registration of tool specifications in the tools array returned by ListToolsRequestSchema handler, including getEntityListsTool.
    const tools = [
      // Entity tools
      getEntityTool,
      getEntitesTool,
      searchEntitesTool,
      getEntityExtensionsTool,
      getEntityRelationshipsTool,
      getEntityConnectionsTool,
      getEntityListsTool,
      // Relationship tools
      getRelationshipTool,
    ];
  • API helper method called by the handler to fetch entity lists from LittleSis API endpoint /entities/{id}/lists.
    static async getEntityLists(id: number): Promise<LittleSisApiResponse<List[]>> {
      return makeApiRequest<List[]>(`/entities/${id}/lists`);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Get') but lacks details on permissions, rate limits, pagination, or response format. This is a significant gap for a tool with no structured safety or behavioral hints.

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 a single, efficient sentence with zero waste. It front-loads the core purpose and includes helpful examples, making it appropriately sized and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't cover behavioral aspects like read/write nature, error handling, or return values, which are critical for a tool with no structured metadata. More context is needed to compensate for these gaps.

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?

The schema description coverage is 100%, with the single parameter 'id' documented as 'The entity ID'. The description adds no additional meaning beyond this, such as format constraints or example values. Baseline 3 is appropriate as the schema handles the parameter documentation adequately.

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 clearly states the tool's purpose: 'Get the lists that an entity appears on' specifies the verb ('Get') and resource ('lists'), with examples ('e.g., Fortune 1000, lobbying lists') adding specificity. It distinguishes from siblings like 'get_entity' (general entity data) or 'get_entity_relationships' (connections), though not explicitly named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives is provided. The description implies usage for retrieving list memberships, but it doesn't mention prerequisites (e.g., needing an entity ID), exclusions, or comparisons to siblings like 'search_entities' for broader queries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/code-rabi/littlesis-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server