Skip to main content
Glama
robobobby
by robobobby

fi_search_by_industry

Search for Finnish companies by industry classification to identify market opportunities and analyze competitors. Filter results by location and company form for targeted research.

Instructions

Find Finnish companies by industry (TOL 2008 classification). Useful for market research and competitor analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
industryYesIndustry - either a TOL 2008 code (e.g., '62010' for software) or descriptive text (e.g., 'software', 'restaurant')
locationNoFilter by town/city
company_formNoFilter by company form (OY, OYJ, etc.)
pageNoPage number

Implementation Reference

  • The implementation of the `fi_search_by_industry` tool, including its registration, schema definition, and handler logic.
    server.tool(
      "fi_search_by_industry",
      "Find Finnish companies by industry (TOL 2008 classification). Useful for market research and competitor analysis.",
      {
        industry: z.string().describe("Industry - either a TOL 2008 code (e.g., '62010' for software) or descriptive text (e.g., 'software', 'restaurant')"),
        location: z.string().optional().describe("Filter by town/city"),
        company_form: z.string().optional().describe("Filter by company form (OY, OYJ, etc.)"),
        page: z.number().optional().default(1).describe("Page number"),
      },
      async ({ industry, location, company_form, page }) => {
        const params = { mainBusinessLine: industry };
        if (location) params.location = location;
        if (company_form) params.companyForm = company_form;
        if (page && page > 1) params.page = page;
    
        const data = await apiFetch("/companies", params);
        const companies = data.companies || [];
        const total = data.totalResults || 0;
    
        if (companies.length === 0) {
          return { content: [{ type: "text", text: `No companies found in industry "${industry}".` }] };
        }
    
        const header = `Found ${total.toLocaleString()} companies in "${industry}" (showing ${companies.length}):\n`;
        const results = companies.map((c, i) => `${i + 1}. ${formatCompanySummary(c)}`).join("\n\n");
    
        return { content: [{ type: "text", text: header + "\n" + results }] };
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description mentions the TOL 2008 classification system and suggests use cases, but it doesn't disclose important behavioral traits such as whether this is a read-only operation, potential rate limits, authentication requirements, pagination behavior (implied by the 'page' parameter but not explained), or what the output format looks like. For a search tool with no annotation coverage, this leaves significant gaps.

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?

The description is appropriately concise with two sentences that each serve a purpose: the first states the core functionality, and the second suggests use cases. It's front-loaded with the main purpose. There's no unnecessary repetition or fluff, though it could potentially be more structured with explicit guidance.

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

Completeness2/5

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

Given the complexity of a company search tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (company details, counts, etc.), how results are structured, pagination behavior, or error conditions. The use case hint is helpful but insufficient for an agent to fully understand the tool's behavior and output.

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%, meaning all parameters are documented in the input schema. The description adds minimal value beyond the schema: it mentions the TOL 2008 classification for the 'industry' parameter and suggests use cases, but doesn't provide additional semantic context for parameters like 'location' or 'company_form'. With high schema coverage, the baseline score of 3 is appropriate.

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?

The description clearly states the tool's purpose: 'Find Finnish companies by industry (TOL 2008 classification).' It specifies the verb ('Find'), resource ('Finnish companies'), and classification system. However, it doesn't explicitly differentiate from sibling tools like 'fi_search_companies' or 'fi_company_lookup', which appear to be related company search tools.

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?

The description provides implied usage context: 'Useful for market research and competitor analysis.' This suggests when the tool might be appropriate, but it doesn't offer explicit guidance on when to use this tool versus alternatives like 'fi_search_companies' or 'fi_company_lookup', nor does it specify any exclusions or prerequisites for usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/robobobby/mcp-nordic'

If you have feedback or need assistance with the MCP directory API, please join our Discord server