Skip to main content
Glama
OnStartups

Agent.ai MCP Server

by OnStartups

company_research_v2_run_full_research

Run comprehensive company research with configurable sections including overview, products, technology, financials, and competitors. Returns a full JSON report.

Instructions

Run comprehensive company research with configurable sections. Returns full JSON report with all data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain to research (e.g., hubspot.com).
section_company_overviewNoInclude company description, industry, employee count, headquarters.
section_visual_timelineNoInclude AI-generated visual infographic of company milestones and history.
section_product_summaryNoInclude product descriptions and G2 ratings.
section_homepage_screenshotNoInclude screenshot of company homepage.
section_technology_stackNoInclude technologies, social media profiles, and follower counts.
section_wappalyzer_technologiesNoInclude detailed technology detection from Wappalyzer.
section_search_keywordsNoInclude SEO keyword analysis with PPC and organic metrics.
section_financialsNoInclude revenue, market cap, profit margins (public companies).
section_funding_historyNoInclude funding rounds and investors.
section_web_trafficNoInclude website traffic trends and visitor metrics.
section_newsNoInclude recent news and press coverage.
section_peopleNoInclude executives and leadership with LinkedIn URLs.
section_competitorsNoInclude competitor analysis with differentiation.
section_job_openingsNoInclude current job listings.
section_contactNoInclude company contact details.
section_g2_reviewsNoInclude G2 review summary and ratings.
force_refreshNoBypass cache and fetch fresh data.
output_variable_nameYesVariable name for the full research report JSON.research_report
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states the tool returns a JSON report. It omits whether the research is long-running, uses external APIs, requires cache, or has rate limits. The 'force_refresh' parameter hints at caching but is not explained in the description.

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, front-loaded with action and output. No waste. However, it could be more informative while remaining concise.

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?

The tool has 19 parameters, no output schema, and no annotations. The description is too sparse to provide complete context about the research flow, synchronous vs asynchronous behavior, or how to interpret the JSON. Sibling tools indicate a rich ecosystem, but this description fails to connect.

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 coverage is 100%, so baseline is 3. The description adds no value beyond the schema; 'configurable sections' merely echoes the boolean flags. The parameter descriptions in schema are adequate, so the description's contribution is minimal.

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 verb 'Run' and resource 'comprehensive company research' with configurable sections and return of JSON report. While it distinguishes from siblings like 'start_research' by implying full execution, it doesn't explicitly differentiate from 'get_report' or 'answer_question'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. No prerequisites, no warnings about cost or time, no exclusions. The description does not help the agent decide when to choose this tool over others like 'company_research_v2_start_research'.

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/OnStartups/agentai-mcp-server'

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