Skip to main content
Glama

Search employers by name

search_employers
Read-onlyIdempotent

Employers whose name matches, best first. Each result carries its PERM record and the slug that the get endpoint takes. Example: {"q":"acme"}.

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": {
      "q": "<q>"
    },
    "name": "search_employers"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes2 to 120 characters of the name. Example: acme.
limitNoResults to return, 1 to 100. 10 when left out. Example: 25.

Output Schema

NameRequiredDescriptionDefault
asOfYesThe date the data is true for, YYYY-MM-DD, when one applies.
dataYesThe answer, or found: false when no record matched.
pageYesThe page on permtracker.app that shows the same thing. Cite it.
sourceYesWho published the underlying records.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds the ordering trait ("best first") and tells the agent the PERM record and a get-compatible slug ride along with each hit, which is genuine behavioral context, though the return contents are largely restated from the output schema.

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?

Three short sentences, front-loaded with the resource and matching rule, then result payload, then a concrete call example. The example largely duplicates the one already inside the q schema description, which is minor waste rather than a structural flaw.

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?

With full schema coverage, annotations, and an output schema, only a small amount of description is needed. However, for a search tool, the matching semantics (what counts as a name match, how ties are ranked, whether partial tokens hit) remain unexplained, and the relationship to lookup_employer/get_employer is left implicit.

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%: q carries length bounds and an example, and limit carries range and default of 10. The description only repeats the q example ("{\"q\":\"acme\"}") and adds no matching semantics such as prefix vs substring vs fuzzy behavior.

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?

States the resource (employers) and the matching behavior with ranking ("name matches, best first"), so the agent knows this is a relevance-ranked name search. It does not distinguish itself from the sibling lookup_employer or get_employer, leaving the reader to infer whether lookup_employer is an exact-match variant.

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 only implied: the mention that each result carries "the slug that the get endpoint takes" conveys the intended two-step flow (search, then fetch details via get_employer). There is no explicit when-to-use or when-not-to-use guidance and no named alternative such as lookup_employer.

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.