aigroup-finnhub-mcp

finnhub_project_create

Create a project workspace to organize and store financial data from Finnhub API.

Instructions

Create a new project workspace for storing data. Operations: create

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operation": "<operation>"
    },
    "name": "finnhub_project_create"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	Project name (alphanumeric, underscore, hyphen only)
`operation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1Jul 5, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations exist, so description carries full burden. It only states creation, but lacks details on side effects (e.g., duplicate names, persistence), required permissions, or any behavioral traits beyond the obvious.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short, but includes redundant 'Operations: create'. It is not front-loaded with key information and could be more 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?

For a creation tool with no output schema and minimal parameters, the description misses essential context such as uniqueness guarantees, default behavior, and post-creation actions.

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

Parameters2/5

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

Schema coverage is 50% (name has description, operation has enum). Description adds 'Operations: create' which merely restates the enum. No additional parameter context provided.

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 'Create a new project workspace' indicating verb and resource. It distinguishes from sibling 'finnhub_project_list' which lists projects. However, 'Operations: create' is redundant and adds no clarity.

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 versus alternatives. There is no mention of prerequisites, limitations, or when not to use it.

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

Deploy Server