Skip to main content
Glama
code-rabi

LittleSis MCP

by code-rabi

get_entity_extensions

Retrieve entity type classifications and associated details for corporate influence tracking. Identify relationships between persons, organizations, and businesses to support accountability research.

Instructions

Get the types/extensions associated with an entity (Person, Organization, Business, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe entity ID
detailsNoInclude additional details contained within extensions

Implementation Reference

  • The handler function that executes the tool logic: calls LittleSisApi.getEntityExtensions with id and details, formats the JSON response, and handles errors.
    export async function handleGetEntityExtensions(args: any) {
      try {
        const result = await LittleSisApi.getEntityExtensions(args.id, args.details);
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2)
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error fetching entity extensions: ${error instanceof Error ? error.message : 'Unknown error'}`
            }
          ],
          isError: true
        };
      }
    }
  • Tool definition with input schema specifying required 'id' (number) and optional 'details' (boolean).
    export const getEntityExtensionsTool: Tool = {
      name: 'get_entity_extensions',
      description: 'Get the types/extensions associated with an entity (Person, Organization, Business, etc.)',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'number',
            description: 'The entity ID'
          },
          details: {
            type: 'boolean',
            description: 'Include additional details contained within extensions',
            default: false
          }
        },
        required: ['id']
      }
    };
  • src/index.ts:72-81 (registration)
    Registration of tool handlers mapping 'get_entity_extensions' to handleGetEntityExtensions function, used by the CallToolRequestSchema 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,
    };
  • API client method that performs the HTTP request to LittleSis API for entity extensions.
    static async getEntityExtensions(id: number, details: boolean = false): Promise<LittleSisApiResponse<Extension[]>> {
      const detailsParam = details ? '?details=TRUE' : '';
      return makeApiRequest<Extension[]>(`/entities/${id}/extensions${detailsParam}`);
    }
  • src/index.ts:58-69 (registration)
    Tool list registration including getEntityExtensionsTool for ListToolsRequestSchema.
    const tools = [
      // Entity tools
      getEntityTool,
      getEntitesTool,
      searchEntitesTool,
      getEntityExtensionsTool,
      getEntityRelationshipsTool,
      getEntityConnectionsTool,
      getEntityListsTool,
      // Relationship tools
      getRelationshipTool,
    ];
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves data ('Get'), implying a read-only operation, but doesn't disclose critical behaviors such as error handling (e.g., for invalid IDs), rate limits, authentication needs, or what happens if extensions are missing. The description adds minimal context beyond the basic action, leaving gaps for a tool with no annotation coverage.

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 without unnecessary words. It uses parentheses for examples (Person, Organization, Business, etc.) to add clarity concisely. Every part of the sentence earns its place, making it well-structured and easy to parse quickly.

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's moderate complexity (2 parameters, no annotations, no output schema), the description is incomplete. It lacks details on return values (e.g., format of extensions), error conditions, and behavioral traits like idempotency or side effects. While the schema covers parameters, the description doesn't address broader context needed for reliable use, especially without annotations or output schema to fill 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?

Schema description coverage is 100%, with both parameters (id and details) fully documented in the schema. The description doesn't add any meaning beyond the schema—it doesn't explain parameter interactions, provide examples, or clarify semantics like what 'additional details' entail. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 verb 'Get' and the resource 'types/extensions associated with an entity', with examples of entity types (Person, Organization, Business, etc.). It distinguishes this from siblings like get_entity (which likely retrieves basic entity data) and get_entity_connections/relationships (which focus on relational data), though it doesn't explicitly name alternatives. The purpose is specific but could be more precise about what 'types/extensions' entail.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't specify prerequisites (e.g., needing an entity ID from another tool), exclusions, or compare it to siblings like get_entity (which might include some extension data) or search_entities. Usage is implied only by the tool name and description, with no explicit context for selection.

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