Skip to main content
Glama
code-rabi

LittleSis MCP

by code-rabi

get_entity

Retrieve detailed information about a specific person or organization using its unique LittleSis ID to access corporate influence data and relationships.

Instructions

Get detailed information about a specific entity (person or organization) from LittleSis by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe unique numerical ID of the entity in LittleSis database

Implementation Reference

  • The handleGetEntity function that executes the get_entity tool: extracts id from args, calls LittleSisApi.getEntity, formats result as text content or error.
    export async function handleGetEntity(args: any) {
      try {
        const result = await LittleSisApi.getEntity(args.id);
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2)
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error fetching entity: ${error instanceof Error ? error.message : 'Unknown error'}`
            }
          ],
          isError: true
        };
      }
    }
  • Tool schema definition for get_entity, specifying name, description, and inputSchema requiring numeric 'id'.
    export const getEntityTool: Tool = {
      name: 'get_entity',
      description: 'Get detailed information about a specific entity (person or organization) from LittleSis by ID',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'number',
            description: 'The unique numerical ID of the entity in LittleSis database'
          }
        },
        required: ['id']
      }
    };
  • src/index.ts:72-81 (registration)
    Registration of get_entity tool handler in the toolHandlers mapping used by 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,
    };
  • src/index.ts:59-69 (registration)
    Inclusion of getEntityTool in the tools array returned by ListToolsRequestSchema handler.
      // Entity tools
      getEntityTool,
      getEntitesTool,
      searchEntitesTool,
      getEntityExtensionsTool,
      getEntityRelationshipsTool,
      getEntityConnectionsTool,
      getEntityListsTool,
      // Relationship tools
      getRelationshipTool,
    ];
  • LittleSisApi.getEntity static method called by the handler to fetch entity data from LittleSis API.
    static async getEntity(id: number): Promise<LittleSisApiResponse<Entity>> {
      return makeApiRequest<Entity>(`/entities/${id}`);
    }
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 it 'Get[s] detailed information,' which implies a read-only operation, but doesn't specify aspects like authentication requirements, rate limits, error handling, or what 'detailed information' includes (e.g., fields returned). This leaves significant 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 ('Get detailed information about a specific entity') and includes essential qualifiers ('person or organization,' 'from LittleSis by ID') without unnecessary words. Every part earns its place, making it highly concise and well-structured.

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

Completeness3/5

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

Given the tool's low complexity (1 parameter, no nested objects) and 100% schema coverage, the description is minimally adequate. However, with no annotations and no output schema, it fails to address behavioral aspects like authentication or return format, which are important for completeness. It meets basic needs but has clear gaps in context.

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 'id' parameter fully documented in the schema as 'The unique numerical ID of the entity in LittleSis database.' The description adds minimal value by mentioning 'by ID,' which is already covered. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't significantly enhance parameter understanding beyond the schema.

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 'detailed information about a specific entity (person or organization) from LittleSis by ID', making the purpose understandable. However, it doesn't explicitly differentiate this tool from its siblings like 'get_entities' (plural retrieval) or 'get_entity_connections' (relationship-focused retrieval), which would be needed for a perfect score.

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 like 'get_entities' (for multiple entities) or 'search_entities' (for finding entities by criteria other than ID). It mentions 'by ID' but doesn't clarify that this is the primary use case over other methods, leaving usage context implied rather than explicit.

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