Skip to main content
Glama
code-rabi

LittleSis MCP

by code-rabi

get_entities

Retrieve detailed information about multiple corporate entities simultaneously to analyze relationships and track corporate influence for accountability research.

Instructions

Get information about multiple entities at once (up to 300 entities per request)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesArray of entity IDs to retrieve (maximum 300)

Implementation Reference

  • The handler function that implements the core logic of the 'get_entities' tool. It calls LittleSisApi.getEntities with the provided ids and returns a formatted text response with JSON data or an error message.
    export async function handleGetEntities(args: any) {
      try {
        const result = await LittleSisApi.getEntities(args.ids);
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2)
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error fetching entities: ${error instanceof Error ? error.message : 'Unknown error'}`
            }
          ],
          isError: true
        };
      }
  • The Tool definition providing the schema, name, and description for the 'get_entities' tool, used in tool listing.
    export const getEntitesTool: Tool = {
      name: 'get_entities',
      description: 'Get information about multiple entities at once (up to 300 entities per request)',
      inputSchema: {
        type: 'object',
        properties: {
          ids: {
            type: 'array',
            items: {
              type: 'number'
            },
            description: 'Array of entity IDs to retrieve (maximum 300)',
            maxItems: 300
          }
        },
        required: ['ids']
      }
    };
  • src/index.ts:72-81 (registration)
    The toolHandlers object that registers the 'get_entities' tool name to its handler function handleGetEntities, used in the call tool request handler.
    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,
    };
  • The LittleSisApi.getEntities static method, which performs the actual API request to fetch multiple entities and is called by the tool handler.
    static async getEntities(ids: number[]): Promise<LittleSisApiResponse<Entity[]>> {
      if (ids.length > 300) {
        throw new Error('Maximum 300 entities per request');
      }
      return makeApiRequest<Entity[]>(`/entities?ids=${ids.join(',')}`);
    }
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 only states the batch retrieval capability and limit (300 entities), but doesn't describe the return format, whether it's paginated, error handling for invalid IDs, authentication requirements, rate limits, or performance characteristics. For a read operation with zero annotation coverage, this leaves significant gaps.

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 that front-loads the core purpose and includes the key constraint (300 entity limit). There's zero wasted text, and every word earns its place by providing essential information about the tool's scope.

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 tool has no annotations and no output schema, the description is incomplete. It doesn't explain what 'information' is returned, the response format, or any behavioral aspects beyond the batch limit. For a tool that presumably returns entity data, this leaves the agent guessing about the output structure and important operational details.

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 input schema has 100% description coverage, with the 'ids' parameter fully documented in the schema (array of numbers, max 300 items). The description adds no additional parameter semantics beyond what's already in the schema - it merely repeats the 300-entity limit. Baseline 3 is appropriate when the schema does the heavy lifting.

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 information about multiple entities at once' specifies the verb (get) and resource (entities), with the scope (multiple, up to 300 per request) distinguishing it from the sibling 'get_entity' which presumably handles single entities. However, it doesn't explicitly differentiate from other sibling tools like 'search_entities' or 'get_entity_lists'.

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

Usage Guidelines3/5

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

The description implies usage when needing information about multiple entities (vs. single entities), but provides no explicit guidance on when to use this tool versus alternatives like 'search_entities' or 'get_entity_lists'. It mentions the batch capability (up to 300 entities) which suggests a use case, but lacks clear exclusions or prerequisites.

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