Skip to main content
Glama

Corporate Exception Report

corporate_exception_report

Enterprise Change Report

Pricing: {"unit": "credits", "options": [{"chapter_name": "License", "per_run": 1518}, {"chapter_name": "GovRel", "per_run": 1419}, {"chapter_name": "R&D", "per_run": 1749}, {"chapter_name": "Reputation", "per_run": 8481}, {"chapter_name": "Ops", "per_run": 1749}, {"chapter_name": "GeneralRisks", "per_run": 1617}, {"chapter_name": "Profile", "per_run": 1749}, {"chapter_name": "Cost", "per_run": 1386}, {"chapter_name": "Compliance", "per_run": 1419}, {"chapter_name": "Competition", "per_run": 1452}, {"chapter_name": "Brand", "per_run": 3168}, {"chapter_name": "HR", "per_run": 1419}, {"chapter_name": "ALL", "per_run": 26400}]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pidYesInternal company ID for the target enterprise, obtained from the search_company_candidates MCP tool (e.g. a77828f060c866441f2403384b271e63 for Tesla, Inc.).
chapter_nameNoException domain chapter to generate. Omit or use ALL for the full corporate exception report.ALL

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedOutput schema / definitions
      Added value: +{
      +  "sub_section": {
      +    "properties": {
      +      "section_texts": {
      +        "description": "Array of sub-section text paragraphs, formatted in Markdown for detailed and structured content including headings, bullet points, tables, and hyperlinks to ensure professional and informative corporate exception subsections.",
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "section_title": {
      +        "description": "Sub-section title.",
      +        "type": "string"
      +      },
      +      "sub_sections": {
      +        "description": "Nested array of sub-sections.",
      +        "items": {
      +          "$ref": "#/definitions/sub_section"
      +        },
      +        "type": "array"
      +      }
      +    },
      +    "required": [
      +      "section_title",
      +      "sub_sections",
      +      "section_texts"
      +    ],
      +    "type": "object"
      +  }
      +}
    • changedOutput schema / oneOf
      Previous value: -[
      -  {
      -    "description": "Text or Markdown response generated by the agent. Returned when the task is not yet completed, failed, cancelled, or requires user input (e.g. validation prompts, error messages, or clarification requests).",
      -    "properties": {
      -      "text": {
      -        "description": "Text or Markdown response generated by the agent. Returned when the task is not yet completed, failed, cancelled, or requires user input (e.g. validation prompts, error messages, or clarification requests).",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "text"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "definitions": {
      -      "sub_section": {
      -        "properties": {
      -          "section_texts": {
      -            "description": "Array of sub-section text paragraphs, formatted in Markdown for detailed and structured content including headings, bullet points, tables, and hyperlinks to ensure professional and informative corporate exception subsections.",
      -            "items": {
      -              "type": "string"
      -            },
      -            "type": "array"
      -          },
      -          "section_title": {
      -            "description": "Sub-section title.",
      -            "type": "string"
      -          },
      -          "sub_sections": {
      -            "description": "Nested array of sub-sections.",
      -            "items": {
      -              "$ref": "#/definitions/sub_section"
      -            },
      -            "type": "array"
      -          }
      -        },
      -        "required": [
      -          "section_title",
      -          "sub_sections",
      -          "section_texts"
      -        ],
      -        "type": "object"
      -      }
      -    },
      -    "description": "Structured corporate exception report output for enterprise analysis.",
      -    "properties": {
      -      "data": {
      -        "properties": {
      -          "chapter_infos": {
      -            "description": "Array of chapter information in the corporate exception report.",
      -            "items": {
      -              "properties": {
      -                "en": {
      -                  "properties": {
      -                    "chapter_name": {
      -                      "description": "Chapter name in English.",
      -                      "type": "string"
      -                    },
      -                    "chapter_texts": {
      -                      "description": "Array of chapter text paragraphs in English, formatted in Markdown for structured presentation including headings, lists, tables, and links to provide comprehensive and professional corporate exception content.",
      -                      "items": {
      -                        "type": "string"
      -                      },
      -                      "type": "array"
      -                    },
      -                    "sub_sections": {
      -                      "description": "Array of sub-sections in English.",
      -                      "items": {
      -                        "$ref": "#/definitions/sub_section"
      -                      },
      -                      "type": "array"
      -                    }
      -                  },
      -                  "required": [
      -                    "chapter_name",
      -                    "sub_sections",
      -                    "chapter_texts"
      -                  ],
      -                  "type": "object"
      -                },
      -                "zh": {
      -                  "properties": {
      -                    "chapter_name": {
      -                      "description": "Chapter name in Chinese.",
      -                      "type": "string"
      -                    },
      -                    "chapter_texts": {
      -                      "description": "Array of chapter text paragraphs in Chinese, formatted in Markdown for structured presentation including headings, lists, tables, and links to provide comprehensive and professional corporate exception content.",
      -                      "items": {
      -                        "type": "string"
      -                      },
      -                      "type": "array"
      -                    },
      -                    "sub_sections": {
      -                      "description": "Array of sub-sections in Chinese.",
      -                      "items": {
      -                        "$ref": "#/definitions/sub_section"
      -                      },
      -                      "type": "array"
      -                    }
      -                  },
      -                  "required": [
      -                    "chapter_name",
      -                    "sub_sections",
      -                    "chapter_texts"
      -                  ],
      -                  "type": "object"
      -                }
      -              },
      -              "required": [
      -                "en"
      -              ],
      -              "type": "object"
      -            },
      -            "type": "array"
      -          },
      -          "languages": {
      -            "description": "Array of language codes indicating the languages included in the response, where 'zk' represents Chinese and 'en' represents English.",
      -            "items": {
      -              "type": "string"
      -            },
      -            "type": "array"
      -          },
      -          "report_infos": {
      -            "description": "Dictionary containing report metadata in English and Chinese.",
      -            "properties": {
      -              "en": {
      -                "properties": {
      -                  "report_date": {
      -                    "description": "Report generation date in English.",
      -                    "type": "string"
      -                  },
      -                  "report_name": {
      -                    "description": "Full report name in English.",
      -                    "type": "string"
      -                  },
      -                  "report_type": {
      -                    "description": "Type of the report in English.",
      -                    "type": "string"
      -                  }
      -                },
      -                "required": [
      -                  "report_date",
      -                  "report_name",
      -                  "report_type"
      -                ],
      -                "type": "object"
      -              },
      -              "zh": {
      -                "properties": {
      -                  "report_date": {
      -                    "description": "Report generation date in Chinese.",
      -                    "type": "string"
      -                  },
      -                  "report_name": {
      -                    "description": "Full report name in Chinese.",
      -                    "type": "string"
      -                  },
      -                  "report_type": {
      -                    "description": "Type of the report in Chinese.",
      -                    "type": "string"
      -                  }
      -                },
      -                "required": [
      -                  "report_date",
      -                  "report_name",
      -                  "report_type"
      -                ],
      -                "type": "object"
      -              }
      -            },
      -            "required": [
      -              "en"
      -            ],
      -            "type": "object"
      -          }
      -        },
      -        "required": [
      -          "languages",
      -          "report_infos",
      -          "chapter_infos"
      -        ],
      -        "type": "object"
      -      },
      -      "type": {
      -        "description": "Indicates structured corporate exception report output.",
      -        "enum": [
      -          "results"
      -        ]
      -      }
      -    },
      -    "required": [
      -      "type",
      -      "data"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "description": "Text or Markdown response generated by the agent. Returned when the task is not yet completed, failed, cancelled, or requires user input (e.g. validation prompts, error messages, or clarification requests).",
      +    "properties": {
      +      "text": {
      +        "description": "Text or Markdown response generated by the agent. Returned when the task is not yet completed, failed, cancelled, or requires user input (e.g. validation prompts, error messages, or clarification requests).",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "text"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "description": "Structured corporate exception report output for enterprise analysis.",
      +    "properties": {
      +      "data": {
      +        "properties": {
      +          "chapter_infos": {
      +            "description": "Array of chapter information in the corporate exception report.",
      +            "items": {
      +              "properties": {
      +                "en": {
      +                  "properties": {
      +                    "chapter_name": {
      +                      "description": "Chapter name in English.",
      +                      "type": "string"
      +                    },
      +                    "chapter_texts": {
      +                      "description": "Array of chapter text paragraphs in English, formatted in Markdown for structured presentation including headings, lists, tables, and links to provide comprehensive and professional corporate exception content.",
      +                      "items": {
      +                        "type": "string"
      +                      },
      +                      "type": "array"
      +                    },
      +                    "sub_sections": {
      +                      "description": "Array of sub-sections in English.",
      +                      "items": {
      +                        "$ref": "#/definitions/sub_section"
      +                      },
      +                      "type": "array"
      +                    }
      +                  },
      +                  "required": [
      +                    "chapter_name",
      +                    "sub_sections",
      +                    "chapter_texts"
      +                  ],
      +                  "type": "object"
      +                },
      +                "zh": {
      +                  "properties": {
      +                    "chapter_name": {
      +                      "description": "Chapter name in Chinese.",
      +                      "type": "string"
      +                    },
      +                    "chapter_texts": {
      +                      "description": "Array of chapter text paragraphs in Chinese, formatted in Markdown for structured presentation including headings, lists, tables, and links to provide comprehensive and professional corporate exception content.",
      +                      "items": {
      +                        "type": "string"
      +                      },
      +                      "type": "array"
      +                    },
      +                    "sub_sections": {
      +                      "description": "Array of sub-sections in Chinese.",
      +                      "items": {
      +                        "$ref": "#/definitions/sub_section"
      +                      },
      +                      "type": "array"
      +                    }
      +                  },
      +                  "required": [
      +                    "chapter_name",
      +                    "sub_sections",
      +                    "chapter_texts"
      +                  ],
      +                  "type": "object"
      +                }
      +              },
      +              "required": [
      +                "en"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "languages": {
      +            "description": "Array of language codes indicating the languages included in the response, where 'zk' represents Chinese and 'en' represents English.",
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "report_infos": {
      +            "description": "Dictionary containing report metadata in English and Chinese.",
      +            "properties": {
      +              "en": {
      +                "properties": {
      +                  "report_date": {
      +                    "description": "Report generation date in English.",
      +                    "type": "string"
      +                  },
      +                  "report_name": {
      +                    "description": "Full report name in English.",
      +                    "type": "string"
      +                  },
      +                  "report_type": {
      +                    "description": "Type of the report in English.",
      +                    "type": "string"
      +                  }
      +                },
      +                "required": [
      +                  "report_date",
      +                  "report_name",
      +                  "report_type"
      +                ],
      +                "type": "object"
      +              },
      +              "zh": {
      +                "properties": {
      +                  "report_date": {
      +                    "description": "Report generation date in Chinese.",
      +                    "type": "string"
      +                  },
      +                  "report_name": {
      +                    "description": "Full report name in Chinese.",
      +                    "type": "string"
      +                  },
      +                  "report_type": {
      +                    "description": "Type of the report in Chinese.",
      +                    "type": "string"
      +                  }
      +                },
      +                "required": [
      +                  "report_date",
      +                  "report_name",
      +                  "report_type"
      +                ],
      +                "type": "object"
      +              }
      +            },
      +            "required": [
      +              "en"
      +            ],
      +            "type": "object"
      +          }
      +        },
      +        "required": [
      +          "languages",
      +          "report_infos",
      +          "chapter_infos"
      +        ],
      +        "type": "object"
      +      },
      +      "type": {
      +        "description": "Indicates structured corporate exception report output.",
      +        "enum": [
      +          "results"
      +        ]
      +      }
      +    },
      +    "required": [
      +      "type",
      +      "data"
      +    ],
      +    "type": "object"
      +  }
      +]
  2. First observed

TDQS

C2.3/5.0
Behavior2/5

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

The annotation openWorldHint=true is vague, and the description does not disclose any behavioral traits beyond the pricing. It does not mention output format, cost implications, rate limits, or that it triggers a long-running generation. With openWorldHint, the agent might expect the tool to return data, but the description only discusses cost, leaving the actual behavior unclear.

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

Conciseness2/5

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

The description is extremely concise (one paragraph) but is filled with pricing JSON that is irrelevant to the tool's function. It is not well-structured for understanding the tool's purpose; the important information is buried under pricing data. The description could be more focused and informative.

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 tool with a complex output (generating a corporate exception report), the description is severely lacking. It does not explain what the report contains, how to interpret the output, or how it relates to the many sibling enterprise_change_* tools. The presence of an output schema helps, but the description does not provide needed context about the report's purpose or usage.

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?

The input schema already has high coverage (100%), with descriptions for both pid and chapter_name, including an example for pid. The description adds no additional parameter semantics, but given the schema's completeness, a baseline of 3 is appropriate; however, the description also includes pricing options that might help understand the chapter_name values, slightly elevating to 4.

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

Purpose2/5

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

The tool name and title are clear that it generates a corporate exception report, but the description is misleading: it says 'Enterprise Change Report' not 'Corporate Exception Report', which could confuse the agent. It does not specify the verb or resource clearly, and the description solely contains pricing information, which obscures the actual purpose.

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?

There is no guidance on when to use this tool versus alternatives. The sibling tools include many enterprise_change_* tools that appear to generate chapter-specific reports, so this tool (corporate_exception_report) likely generates the whole report or a chapter, but the description does not clarify this. No exclusions or alternatives are mentioned.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, with consistent scopes (e.g., chain_* vs park_* vs company_* vs gov_data_*). The list/num pairs are clearly differentiated. A few overlapping concepts exist (e.g., company_patent vs enterprise_change_innovation) but descriptions clarify the angle. Some typos (company_randomin_spection) don't cause ambiguity.

Naming Consistency4/5

Naming follows a mostly predictable snake_case pattern with prefixes indicating domain (chain_, park_, company_, enterprise_change_, gov_data_, poi_data_, business_surrounding_, cbd_surrounding_). Most tools use <prefix>_<entity>_<action> or <prefix>_<subject>. A few outliers (sg_chokepoint, tariff_calc, corporate_exception_report) deviate but are few and recognizable.

Tool Count1/5

With 198 tools, this is far beyond any reasonable scope for a single server. It exceeds even the 'extreme mismatch' threshold of 50+ tools. The large number makes selection and discoverability challenging, despite good internal organization.

Completeness4/5

The tool surface covers a vast range of enterprise data, regional macro stats, POI details, supply chain analysis, and tariffs. It appears to cover the primary domain comprehensively, with only minor potential gaps (e.g., no direct tool for company debt ratings or specific product catalogs, but these are addressed via enterprise_change_* and company_* tools).

Resources