Skip to main content
Glama

get_competitive_positioning

Read-only

Analyze competitor strengths and weaknesses to develop effective sales strategies, identify key differentiators, and prepare for competitive discussions in enterprise deals.

Instructions

Gives you the battlecard for a specific competitor — where you win, where they'll attack, which questions to plant in the buyer's mind, and which landmines to avoid.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
competitorNameYesCompetitor company name
competitorFeaturesNoKnown competitor features or capabilities
contextNoAdditional context (e.g., "enterprise deal", "competing on price")
productDescriptionNoA brief description of what the user's product does and who it's for. Infer this from the conversation if the user has already described their product. If the user hasn't mentioned their product yet, ask them: "What does your product do, and who do you sell to?" before calling this tool.
verticalNoThe industry the user sells into (e.g., "fintech", "healthcare", "defense"). Infer from conversation context — the user's product description, company name, or the companies they're asking about. If unclear, ask.
targetRoleNoThe buyer role being evaluated (e.g., "CFO", "CTO", "VP Sales"). Infer from context — often explicit in the user's question. If not mentioned, default to the most senior relevant role for their vertical.

Implementation Reference

  • Definition and input schema for the get_competitive_positioning tool in the static catalog.
    {
      name: 'get_competitive_positioning',
      description: 'Gives you the battlecard for a specific competitor — where you win, where they\'ll attack, which questions to plant in the buyer\'s mind, and which landmines to avoid.',
      annotations: READ_ONLY,
      inputSchema: {
        type: 'object',
        properties: {
          competitorName: { type: 'string', description: 'Competitor company name' },
          competitorFeatures: {
            type: 'array',
            items: { type: 'string' },
            description: 'Known competitor features or capabilities',
          },
          context: {
            type: 'string',
            description: 'Additional context (e.g., "enterprise deal", "competing on price")',
          },
          ...COLD_START_PARAMS,
  • The handler for all tool execution requests, which proxies calls to the Andru backend via the AndruClient.
    server.setRequestHandler(
      CallToolRequestSchema,
      async (request) => {
        if (!client) {
          return {
            content: [{ type: 'text', text: JSON.stringify({ error: 'ANDRU_API_KEY not configured. Tool execution requires an API key.' }) }],
            isError: true,
          };
        }
        const { name, arguments: args } = request.params;
        try {
          return await client.callTool(name, args || {});
  • Client method that performs the actual network request to the backend to execute the specified tool.
    async callTool(name, args) {
      return this.post('/api/mcp/tools/call', { tool: name, arguments: args });
    }
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating safe read operations with open-ended inputs. The description adds valuable behavioral context by specifying the battlecard's components (where you win, attack points, questions to plant, landmines), which goes beyond what annotations provide about operational safety.

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?

The description is a single, efficient sentence that front-loads the core purpose and immediately details the battlecard's four key components. Every element serves a clear purpose with zero wasted words.

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

Completeness4/5

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

For a read-only tool with rich annotations and comprehensive schema documentation, the description provides good contextual completeness. The battlecard metaphor effectively conveys the output's structure and utility, though without an output schema, some details about return format remain unspecified.

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?

With 100% schema description coverage, all parameters are well-documented in the schema. The description doesn't add parameter-specific semantics beyond the battlecard metaphor, but the schema provides comprehensive parameter descriptions including inference guidance for productDescription, vertical, and targetRole.

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?

The description clearly states the tool's purpose with specific verbs ('gives you the battlecard') and resource ('for a specific competitor'), and distinguishes it from siblings by focusing on competitive positioning analysis rather than other sales/marketing functions like prospect discovery or account planning.

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

Usage Guidelines3/5

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

The description implies usage context through the battlecard metaphor (sales/marketing scenarios), but doesn't explicitly state when to use this tool versus alternatives like 'get_capability_profile' or 'get_messaging_framework'. No explicit exclusions or prerequisites are mentioned.

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/geter-andru/andru-revenue-intelligence'

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