HeadStart Jobs

Look a company up

find_company

Read-only

Look a company up in HeadStart's directory by name, typos and aliases allowed: each candidate's key, Boards, openings and match. Nothing is picked; confirm a typo or prefix match with the user. Pass a key as company.

Input Schema

Name	Required	Description	Default
`name`	Yes	A name, or a Board key ('ashby:openai').
`limit`	No	Candidates to list.

Output Schema

Name	Required	Description	Default
`companies`	Yes
`truncated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 27, 2026

changedInput schema / properties / limit / description

Previous value: -"How many candidates to list."New value: +"Candidates to list."

changedInput schema / properties / name / description

Previous value: -"The company's name, or a Board key such as 'ashby:openai'."New value: +"A name, or a Board key ('ashby:openai')."

addedOutput schema / additionalProperties
```
Added value: +false
```
addedOutput schema / properties / companies / items / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / companies / items / required

Added value: +[
+  "key",
+  "name",
+  "boards",
+  "atses",
+  "tech_openings",
+  "match"
+]

Changed3 schema fields changedOct 27, 2026

addedInput schema / properties / limit / description
```
Added value: +"How many candidates to list."
```
addedInput schema / required
```
Added value: +[
+  "name"
+]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "companies": {
+      "items": {
+        "properties": {
+          "atses": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "boards": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "key": {
+            "type": "string"
+          },
+          "match": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "tech_openings": {
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "companies"
+  ],
+  "type": "object"
+}

First observedOct 14, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already establish read-only and open-world behavior, but the description adds useful behavioral context: it returns candidate matches, exposes key/Boards/openings/match, and explicitly does not select anything. This is meaningful beyond the annotations.

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 definition is compact and front-loaded: the lookup action comes first, followed by match behavior and the no-auto-selection constraint. Every sentence adds useful information.

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 an output schema and annotations, the description supplies enough context for correct invocation: fuzzy lookup behavior, candidate output, and the requirement to confirm ambiguous matches. The only notable gap is the misleading `company` reference.

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

Parameters2/5

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

Schema coverage is 100%, so the parameter baseline is 3. However, the description says "Pass a key as `company`", while the actual parameter is named `name` and there is no `company` parameter, which is misleading on top of an otherwise well-documented 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?

States a specific verb and resource: "Look a company up in HeadStart's directory by name". It also notes fuzzy matching and the returned candidate fields, though it does not explicitly distinguish itself from sibling tools such as company_profile.

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

Usage Guidelines4/5

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

Gives clear operational guidance: typos and aliases are allowed, nothing is auto-picked, and ambiguous matches must be confirmed with the user. It stops short of naming alternative tools or stating when to prefer company_profile over this lookup.

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

All HeadStart Jobs tools Inspect

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

Need Help?