Skip to main content
Glama
robobobby
by robobobby

fi_recent_registrations

Discover recently registered Finnish companies to track new business formation trends. Filter results by location, company form, industry, and timeframe.

Instructions

Find recently registered Finnish companies. Great for tracking new business formation trends.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
days_backNoHow many days back to look (default 7)
locationNoFilter by town/city
company_formNoFilter by company form (OY, OYJ, etc.)
business_lineNoFilter by industry
pageNoPage number

Implementation Reference

  • The handler logic for the 'fi_recent_registrations' tool, which calculates the date range and calls the apiFetch helper.
    async ({ days_back, location, company_form, business_line, page }) => {
      const end = new Date();
      const start = new Date(end.getTime() - days_back * 24 * 60 * 60 * 1000);
      const fmt = d => d.toISOString().slice(0, 10);
    
      const params = {
        registrationDateStart: fmt(start),
        registrationDateEnd: fmt(end),
      };
      if (location) params.location = location;
      if (company_form) params.companyForm = company_form;
      if (business_line) params.mainBusinessLine = business_line;
      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 registered in the last ${days_back} days matching your criteria.` }] };
      }
    
      const header = `${total.toLocaleString()} companies registered ${fmt(start)} to ${fmt(end)} (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 }] };
    }
  • Registration of the 'fi_recent_registrations' tool including its schema definition.
    server.tool(
      "fi_recent_registrations",
      "Find recently registered Finnish companies. Great for tracking new business formation trends.",
      {
        days_back: z.number().optional().default(7).describe("How many days back to look (default 7)"),
        location: z.string().optional().describe("Filter by town/city"),
        company_form: z.string().optional().describe("Filter by company form (OY, OYJ, etc.)"),
        business_line: z.string().optional().describe("Filter by industry"),
        page: z.number().optional().default(1).describe("Page number"),
      },
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. It mentions the tool is for 'tracking new business formation trends,' which hints at read-only behavior, but doesn't explicitly state whether it's a read operation, its data source, rate limits, or error handling. This leaves significant gaps in understanding how the tool behaves beyond its basic purpose.

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 description is two concise sentences with zero waste: the first states the purpose, and the second adds contextual value about usage. It's front-loaded with the core function and efficiently structured, earning a top score for brevity and clarity.

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?

Given the tool's moderate complexity (5 parameters, no output schema, no annotations), the description is minimally adequate. It covers the purpose and hints at usage but lacks details on behavioral traits, output format, or error handling. With no annotations to fill gaps, it's complete enough for basic understanding but leaves room for improvement in operational context.

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?

The input schema has 100% description coverage, with each parameter clearly documented (e.g., 'days_back' for time range, 'location' for filtering). The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage without compensating value.

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 recently registered Finnish companies.' It specifies the verb ('Find') and resource ('recently registered Finnish companies'), making the action and target explicit. However, it doesn't differentiate from sibling tools like 'fi_search_companies' or 'fi_search_by_industry,' which limits its score to 4 instead of 5.

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 with 'Great for tracking new business formation trends,' suggesting it's suited for trend analysis. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., 'fi_search_companies' for broader searches) or any exclusions, so it doesn't fully meet the criteria for higher scores.

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