Skip to main content
Glama

Find jobs few companies do well

find_niches
Read-onlyIdempotent

Use cases agents bring to each category, with how many companies fully fit each. Use it to find under-served jobs or who does a job well.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_niches"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoWords that must all appear in the use case's name, asks, category or capabilities
areaNoAn area slug, e.g. payments
sortNoopen (fewest full fits, then most demand; the default), demand, or crowded
viewNouseCases (the default) or capabilities
limitNoResults to return (default 15)
categoryNoA category slug, e.g. web-scrapers
minWeightNoOnly use cases at least this large a share of their category's work
capabilityNoA capability id or prefix, e.g. web.scrape or payments.
competitionNoHow many companies fully fit: none, one, few (2 or 3), crowded (4 or more)
maxCompaniesNoAt most this many companies with a full fit (with view=capabilities: with the tag)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description's only added behavioral detail is that output includes company fit counts per use case, which is modest but relevant context. It says nothing about result caps, ordering defaults, or pagination behavior beyond what the schema enumerates.

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?

Two sentences with no filler, and the value proposition is in the first line. Minor deduction for the vague noun-phrase opener and the pronoun 'it' in the second sentence, which make the lead sentence slower to interpret than it needs to be.

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?

For a 10-parameter, zero-required query tool with no output schema, the description does at least sketch the return shape (use cases plus company fit counts), which partially compensates for the missing output schema. But the dual view modes, the niche/'open' concept, and how filters combine are all left entirely to the schema, so the definition is only minimally sufficient.

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% across all 10 parameters, including three enums and clear per-field explanations, so the schema carries the full semantic load. The description adds no parameter guidance at all — it does not explain q, area, competition, or the useCases vs capabilities view distinction. Baseline 3 applies when the schema is this complete.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys that results are use cases per category paired with a count of companies that fully fit, and the title 'Find jobs few companies do well' hints at the niche-finding intent. However, it never states a clear verb such as 'list' or 'search', and the opening phrase 'Use cases agents bring to each category' is awkward jargon that takes effort to parse. It is roughly distinguishable from siblings like list_capabilities or get_use_case, but only by inference.

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?

It gives one explicit usage cue: 'Use it to find under-served jobs or who does a job well,' which maps to the open/competition filtering direction. There are no exclusions, no prerequisites, and no named alternatives for when a different sibling tool would be better.

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