Skip to main content
Glama

Company Profile

company_profile

Retrieve a comprehensive company profile by ticker, CIK, or name, including SEC filings, OTC data, patents, trademarks, and court cases from multiple datasets.

Instructions

Get a unified company profile across all Verilex datasets. Searches by ticker symbol, SEC CIK number, or company name. Returns SEC filings, OTC data (shell risk, financials), patent portfolio, trademark registrations, and court cases — all in one response. This is the premium cross-dataset intelligence endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierYesCompany identifier: ticker symbol (e.g. AAPL), CIK number (e.g. 0000320193), or company name

Implementation Reference

  • The async handler function for the company_profile tool. It takes an identifier (ticker/CIK/name), calls apiGet on /api/v1/company/:identifier, and returns the JSON result or an error message.
    async ({ identifier }) => {
      const res = await apiGet<Record<string, unknown>>(
        `/api/v1/company/${encodeURIComponent(identifier)}`,
      );
    
      if (!res.ok) {
        const msg =
          res.status === 404
            ? `No data found for '${identifier}' across any dataset.`
            : `API error (${res.status}): ${JSON.stringify(res.data)}`;
        return {
          content: [{ type: "text" as const, text: msg }],
          isError: res.status !== 404,
        };
      }
    
      return {
        content: [
          { type: "text" as const, text: JSON.stringify(res.data, null, 2) },
        ],
      };
    },
  • Input schema for company_profile: a single 'identifier' field (string, 1-100 chars, describing ticker/CIK/name).
    inputSchema: {
      identifier: z
        .string()
        .min(1)
        .max(100)
        .describe("Company identifier: ticker symbol (e.g. AAPL), CIK number (e.g. 0000320193), or company name"),
    },
  • Registration of the 'company_profile' tool using server.registerTool() with name, metadata (title, description, inputSchema), and handler.
    server.registerTool(
      "company_profile",
      {
        title: "Company Profile",
        description:
          "Get a unified company profile across all Verilex datasets. Searches by ticker symbol, " +
          "SEC CIK number, or company name. Returns SEC filings, OTC data (shell risk, financials), " +
          "patent portfolio, trademark registrations, and court cases — all in one response. " +
          "This is the premium cross-dataset intelligence endpoint.",
        inputSchema: {
          identifier: z
            .string()
            .min(1)
            .max(100)
            .describe("Company identifier: ticker symbol (e.g. AAPL), CIK number (e.g. 0000320193), or company name"),
        },
      },
      async ({ identifier }) => {
        const res = await apiGet<Record<string, unknown>>(
          `/api/v1/company/${encodeURIComponent(identifier)}`,
        );
    
        if (!res.ok) {
          const msg =
            res.status === 404
              ? `No data found for '${identifier}' across any dataset.`
              : `API error (${res.status}): ${JSON.stringify(res.data)}`;
          return {
            content: [{ type: "text" as const, text: msg }],
            isError: res.status !== 404,
          };
        }
    
        return {
          content: [
            { type: "text" as const, text: JSON.stringify(res.data, null, 2) },
          ],
        };
      },
    );
  • src/index.ts:46-46 (registration)
    Top-level wiring: registerCompanyTools(server) is called from src/index.ts to register all company tools including company_profile.
    registerCompanyTools(server);
  • The apiGet helper used by the handler to make HTTP GET requests to the Verilex API.
    export async function apiGet<T = unknown>(
      path: string,
      params?: Record<string, string | number | undefined>,
    ): Promise<ApiResponse<T>> {
      const url = buildUrl(path, params);
    
      const headers: Record<string, string> = {
        Accept: "application/json",
        "User-Agent": "verilex-mcp-server/0.1.0",
      };
    
      // Forward x402 payment token if present in env (for paid endpoints)
      const paymentToken = process.env.VERILEX_PAYMENT_TOKEN;
      if (paymentToken) {
        headers["X-Payment-Token"] = paymentToken;
      }
    
      const res = await fetch(url, { headers });
      const data = (await res.json()) as T;
    
      const stale = res.headers.get("X-Data-Stale");
      const lastUpdated = res.headers.get("X-Data-Last-Updated");
      const ageSeconds = res.headers.get("X-Data-Age-Seconds");
    
      return {
        ok: res.ok,
        status: res.status,
        data,
        stale: stale === "true",
        lastUpdated: lastUpdated ?? undefined,
        ageSeconds: ageSeconds ? Number(ageSeconds) : undefined,
      };
    }
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions the tool is 'premium' and 'cross-dataset,' implying aggregation and potential cost, but it does not detail authentication requirements, rate limits, or any side effects. This leaves significant gaps for an AI agent.

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 two sentences with no wasted words. It front-loads the purpose and concisely lists the output types in the second sentence. Every sentence adds value, and the structure makes the tool's capability immediately clear.

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

Completeness4/5

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

Given no annotations and no output schema, the description adequately covers the input and expected outputs. It lists multiple data types returned. However, it lacks details about the response format, pagination, or limitations, which would be helpful for a premium endpoint. Still, for a single-parameter tool, it is mostly complete.

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 single parameter 'identifier' is fully described in the input schema with examples (ticker, CIK, name). The description confirms these possibilities but adds no additional semantic value beyond what the schema already provides. With 100% schema coverage, a baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 a unified company profile across all Verilex datasets.' It specifies the input types (ticker, CIK, name) and lists the output categories (SEC filings, OTC data, patents, trademarks, court cases), distinguishing it from sibling tools that focus on individual data types.

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 guidance on when to use this tool versus alternatives. Sibling tools like lookup_otc_ticker, lookup_patent, and get_sec_filing offer individual lookups, but the description does not explain when the unified profile is preferable or when to use specific tools instead.

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/carrierone/verilexdata-mcp'

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