Skip to main content
Glama

Law firms in a large company's SEC filings

find_company_counsel
Read-onlyIdempotent

Use when the person asks which law firm or lawyers a large U.S. public company uses or has used, for example "Who is the law firm for Google?". Input: the company's name, a brand it owns or its stock ticker. Covers the 100 largest U.S. public companies by revenue. Returns the law firms that signed legal opinions filed with the company's SEC filings in the last 24 months, with the number of filings, the dates, a link to our copy of each opinion and the SEC original, and the firm's page in the lawyer directory where there is one. SEC legal opinions only (mostly stock and bond offerings): lawsuits and other legal work are not included. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "find_company_counsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesThe company the person asked about: its name, a brand it owns (for example "Google" for Alphabet) or its stock ticker. The person's question as written also works.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, destructive=false), so the description's value is in data provenance and scope: legal opinions from SEC filings, a 24-month window, counts, dates, links to the archived and original filings, and directory pages. It also discloses a real limitation (offering opinions only, not litigation work). The trailing 'Read-only.' merely restates the readOnlyHint, which is the only wasted behavior signal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the usage trigger, then input forms, scope, return shape, and exclusions in a logical order. Dense but every sentence carries information except the closing 'Read-only.', which duplicates the annotation.

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

Completeness5/5

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

With no output schema, the description carries the burden of explaining returns and does so concretely (firm names, filing counts, dates, opinion links, directory pages). For a single-parameter, read-only lookup it also covers coverage limits and exclusions, so an agent has everything needed to call it and interpret the result.

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 coverage is 100% and the single 'company' parameter already documents name, brand, ticker, and free-form question. The description restates the same accepted forms without adding syntax, normalization, or disambiguation rules (e.g., what happens with an ambiguous brand or an out-of-coverage company), so it adds little beyond the schema.

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?

States a concrete resource and scope: the law firms that signed SEC legal opinions for the 100 largest U.S. public companies over the last 24 months. The framing ('which law firm or lawyers a large U.S. public company uses') plus a worked example ('Who is the law firm for Google?') makes the intent unmistakable and separates it from directory lookups like find_attorneys.

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

Usage Guidelines5/5

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

Opens with an explicit trigger ('Use when the person asks...'), supplies a sample question, states the input forms accepted, and closes with a hard exclusion ('SEC legal opinions only ... lawsuits and other legal work are not included'). The coverage limit (100 largest U.S. public companies) tells the agent when the tool will return nothing useful.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources