incorporation.check_entitlementCheck the selected project's incorporation package entitlement without changing it. This ChatGPT tool never returns a price, purchase URL, or purchasing instructions.
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Output schema / oneOfPrevious value: -[
- {
- "additionalProperties": false,
- "properties": {
- "entitled": {
- "type": "boolean"
- },
- "entitlement_id": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "package_type": {
- "type": "string"
- },
- "price": {
- "type": "string"
- },
- "purchase_url": {
- "type": "string"
- },
- "reason_code": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "source": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "status": {
- "type": "string"
- }
- },
- "required": [
- "entitled",
- "status",
- "source",
- "entitlement_id",
- "reason_code",
- "price",
- "package_type",
- "purchase_url"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "error": {
- "additionalProperties": false,
- "properties": {
- "code": {
- "type": "string"
- },
- "correlation_id": {
- "type": "string"
- },
- "message": {
- "type": "string"
- },
- "retryable": {
- "type": "boolean"
- }
- },
- "required": [
- "code",
- "message",
- "retryable"
- ],
- "type": "object"
- },
- "status": {
- "const": "error"
- }
- },
- "required": [
- "status",
- "error"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "confirmation": {
- "additionalProperties": false,
- "properties": {
- "expires_at": {
- "type": "string"
- },
- "instruction": {
- "type": "string"
- },
- "token": {
- "type": "string"
- }
- },
- "required": [
- "token",
- "expires_at",
- "instruction"
- ],
- "type": "object"
- },
- "preview": {
- "additionalProperties": true,
- "type": "object"
- },
- "status": {
- "const": "confirmation_required"
- }
- },
- "required": [
- "status",
- "confirmation",
- "preview"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "message": {
- "type": "string"
- },
- "next_action": {
- "additionalProperties": true,
- "type": "object"
- },
- "status": {
- "const": "unavailable"
- }
- },
- "required": [
- "status",
- "message",
- "next_action"
- ],
- "type": "object"
- }
-]New value: +[
+ {
+ "additionalProperties": false,
+ "properties": {
+ "entitled": {
+ "type": "boolean"
+ },
+ "entitlement_id": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "guidance": {
+ "type": "string"
+ },
+ "purchase_supported_in_chatgpt": {
+ "type": "boolean"
+ },
+ "reason_code": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "source": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "status": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "entitled",
+ "status",
+ "source",
+ "entitlement_id",
+ "reason_code",
+ "purchase_supported_in_chatgpt",
+ "guidance"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "error": {
+ "additionalProperties": false,
+ "properties": {
+ "code": {
+ "type": "string"
+ },
+ "correlation_id": {
+ "type": "string"
+ },
+ "message": {
+ "type": "string"
+ },
+ "retryable": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "code",
+ "message",
+ "retryable"
+ ],
+ "type": "object"
+ },
+ "status": {
+ "const": "error"
+ }
+ },
+ "required": [
+ "status",
+ "error"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "confirmation": {
+ "additionalProperties": false,
+ "properties": {
+ "expires_at": {
+ "type": "string"
+ },
+ "instruction": {
+ "type": "string"
+ },
+ "token": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "token",
+ "expires_at",
+ "instruction"
+ ],
+ "type": "object"
+ },
+ "preview": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "status": {
+ "const": "confirmation_required"
+ }
+ },
+ "required": [
+ "status",
+ "confirmation",
+ "preview"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "message": {
+ "type": "string"
+ },
+ "next_action": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "status": {
+ "const": "unavailable"
+ }
+ },
+ "required": [
+ "status",
+ "message",
+ "next_action"
+ ],
+ "type": "object"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description reinforces this with 'without changing it.' More importantly, it discloses a behavioral boundary not visible anywhere else: the tool never returns price, purchase URL, or purchasing instructions, which is critical for avoiding overpromising.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no filler. The core purpose is front-loaded in the first sentence, and the second sentence earns its place by stating a crucial limitation.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a low-complexity, read-only, one-parameter tool with an output schema and rich annotations, the description covers the important semantic and behavioral points. Nothing essential is missing for an agent to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, so the description must add meaning. It does by tying project_id to the 'selected project', and since there is only one integer parameter that is straightforward. It could be stronger by stating where the selected project ID comes from, but this is sufficient for a single simple parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Check') and object ('incorporation package entitlement'), scopes it to the selected project, and explicitly notes it does not change anything. This clearly separates it from sibling tools like start_case, cancel_case, or get_case.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explains when to call it: when the selected project's entitlement needs checking. However, it does not name any alternative tools or give explicit when-not-to-use guidance; the 'never returns price/purchase info' line hints at a boundary but does not route the agent elsewhere.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Domain prefixes (crm., cap_table., landing.) clearly separate broad modules, and most tools target a specific resource and action. However, within modules there are boundary overlaps—crm.add_contact_note vs crm.log_activity and cap_table.dilution_preview vs cap_table.simulate_raise—where descriptions must be read carefully to avoid a wrong pick.
The dominant pattern is module.verb_noun (e.g., crm.create_lead, cap_table.update_stakeholder), which is clear and readable. But a subset of top-level tools uses object_verb with flat underscores (e.g., shortlink_create, qr_generate, campaign_archive) and one outlier (campaign_stats) breaks the verb pattern, so conventions are mixed.
86 tools is an extreme surface for any single MCP server, well past the 50+ threshold that makes coherent selection impractical. Even though the features span several business domains, this would be far more usable split into focused servers per module.
The covered domains are broadly complete: cap table, CRM, incorporation, landing, projects, sparkroom, tasks, and validation all have read/write workflows with few dead ends. Minor gaps remain (no campaign listing/update, no branding palette delete/update, no contact deletion) but none of them blocks the main product workflows.