Skip to main content
Glama

Equibles

by io.github.daniel3303
OverviewDiscussionsAdmin

Search Corporate Insiders

SearchInsiders
Read-only

Search the tracked SEC corporate-insider set (directors, officers, 10% owners) by name. Search first requires every punctuation-independent whole query word in the filed legal name, then broadens to any whole word only when no strict row matches; a token inside a different word is not a match. Verified public-name aliases such as Jensen Huang resolve to the SEC owner identity. Returns CIK, role, latest filing company, and location, ordered by recent filing activity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query for insider name
offsetNoNumber of matches to skip before returning rows (default: 0, clamped to 0-100000). For the next page, add the returned row count to the clamped current offset; if the next offset exceeds 100000, narrow the filters instead. Stop when fewer than the effective page size (maxResults clamped to 1-500) are returned, or the response's total has been reached.
maxResultsNoMaximum number of results (default: 10, max: 500; values outside 1-500 are clamped)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / offset / description
      Previous value: -"Number of matches to skip before returning rows — pass the previous call's shown count to page past the maxResults cap (default: 0)"New value: +"Number of matches to skip before returning rows (default: 0, clamped to 0-100000). For the next page, add the returned row count to the clamped current offset; if the next offset exceeds 100000, narrow the filters instead. Stop when fewer than the effective page size (maxResults clamped to 1-500) are returned, or the response's total has been reached."
  2. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Number of matches to skip before returning rows — pass the previous call's shown count to page past the maxResults cap (default: 0)",
+  "type": "integer"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint=false/destructiveHint=false, so safety is covered. The description adds genuine behavioral detail beyond annotations: the two-stage matching rule (all punctuation-independent words first, then any whole word), the no-substring rule, alias resolution (e.g., Jensen Huang), the returned fields, and the ordering by recent filing activity.

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?

A single front-loaded paragraph: the tool's scope comes first, then matching behavior, then return shape. It is dense but every sentence carries decision-relevant information, though the matching-rule sentence is somewhat syntactically heavy.

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?

No output schema exists, but the description compensates by naming the returned fields (CIK, role, latest filing company, location) and the ordering, and the pagination contract is fully documented in the schema. Nothing material for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description goes beyond the schema's terse 'Search query for insider name' by specifying whole-word, punctuation-independent matching semantics and alias behavior for the query parameter, which materially changes how an agent should phrase a query. Offset/maxResults are left entirely to the schema, so not a 5.

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 specific verb ('Search') and resource ('the tracked SEC corporate-insider set') and even enumerates the entity types covered (directors, officers, 10% owners). This clearly separates it from the many sibling search tools (SearchCongressMembers, SearchInstitutions, SearchFunds) that target different entity sets.

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?

Usage is implied: use this to look up insiders by name, and the description explains that matching starts strict and then broadens. However, it never states when NOT to use it, nor names alternatives such as GetInsiderOwnership or GetInsiderTransactions for non-name-based insider data, so the agent must infer routing.

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

All Equibles toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources