Skip to main content
Glama
trippborstel-hub

northwood-carbon MCP server

list_portcos

List all Northwood portfolio companies with sector, status, revenue, EBITDA, facilities count, and carbon metrics. Provides starting point for portfolio-level questions.

Instructions

List all 10 Northwood portfolio companies with sector, status, and headline metrics.

Returns a list of dicts containing: slug, name, sector, fund, status, revenue ($M), ebitda ($M), facilities count, data_grade, base_year, target_year, target_reduction_pct.

Use this as the starting point for portfolio-level questions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • server.py:73-98 (handler)
    The list_portcos tool handler: a FastMCP tool that lists all portfolio companies with their slug, name, sector, fund, status, revenue (M), EBITDA (M), facilities count, data grade, base year, target year, and target reduction percentage.
    def list_portcos() -> list[dict[str, Any]]:
        """
        List all 10 Northwood portfolio companies with sector, status, and headline metrics.
    
        Returns a list of dicts containing: slug, name, sector, fund, status, revenue ($M),
        ebitda ($M), facilities count, data_grade, base_year, target_year, target_reduction_pct.
    
        Use this as the starting point for portfolio-level questions.
        """
        return [
            {
                "slug": slug,
                "name": p["name"],
                "sector": p["sector"],
                "fund": p["fund"],
                "status": p["status"],
                "revenue_m": p["revenue"],
                "ebitda_m": p["ebitda"],
                "facilities": p["facilities"],
                "data_grade": p["dataGrade"],
                "base_year": p["baseYear"],
                "target_year": p["targetYear"],
                "target_reduction_pct": p["targetReduction"],
            }
            for slug, p in PORTCOS.items()
        ]
  • server.py:72-72 (registration)
    The registration decorator @mcp.tool() that registers list_portcos as an MCP tool on the FastMCP server instance.
    @mcp.tool()
  • Data loading: PORTCOS dict is loaded from data.json and used by list_portcos to build its response.
    # ── Load data ─────────────────────────────────────────────────────────────
    DATA_PATH = Path(__file__).parent / "data.json"
    DATA: dict[str, Any] = json.loads(DATA_PATH.read_text())
    PORTCOS = DATA["PORTCOS"]
    TRAJECTORY = DATA["TRAJECTORY"]
    INITIATIVES = DATA["INITIATIVES"]
    RISK_SUMMARY = DATA["RISK_SUMMARY"]
    ESG_SCORES = DATA["ESG_SCORES"]
    FACILITIES = DATA["FACILITIES"]
Behavior4/5

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

No annotations provided, but description covers that it lists all companies and specifies return fields. No hidden behaviors; adequate for a simple read-only list.

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?

Two sentences, front-loaded with purpose and immediate value, no wasted words.

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

Completeness5/5

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

Given 0 parameters and output schema exists, description still enumerates return fields for clarity. Provides complete starting point for portfolio queries.

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

Parameters4/5

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

Input schema is empty (0 parameters). Description adds no parameter info because none needed. Baseline 4 for 0-param tools.

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

Purpose5/5

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

Description explicitly states 'List all 10 Northwood portfolio companies' with specific fields (sector, status, headline metrics), clearly distinguishing from sibling tools like gap_to_target or get_portco_emissions.

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?

Explicitly says 'Use this as the starting point for portfolio-level questions', indicating when to use. No explicit when-not or alternatives, but context is clear enough.

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/trippborstel-hub/northwood-carbon-mcp'

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