Skip to main content
Glama
Sign In

Chrome-Stats

by com.chrome-stats
OverviewDiscussionsAdmin

Get extension details

get_extension
Read-onlyIdempotent

Retrieve details for one extension or app: publisher, install count, rating, version, and category. Heavier sections are omitted by default — pass include to add store ranks, recent reviews, risk analysis, requested permissions, publisher-email change history, or similar alternatives. Some fields are masked for free plans.

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": {
      "id": "<id>"
    },
    "name": "get_extension"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesChrome extension ID, Edge add-on ID, Firefox add-on slug/GUID, Android package name, or Apple App Store app ID. For example bmnlcjabgnpnenekpadlanbbkooimhnj or com.joinhoney.honeyandroid.
includeNoOptional extra sections: ranks, reviews, risk, permissions, history, alternatives.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description is free to add what they cannot: heavier sections are omitted by default and only added via `include`, which tells the agent the default call is cheap, and some fields are masked for free plans, which prevents misreading partial data as missing data.

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?

Three sentences, zero waste. It front-loads what is returned, then the default/opt-in behavior, then the plan-masking caveat in escalating order of surprise.

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 lookup with no output schema, the description covers the meaningful return fields, the opt-in mechanism, and a data-quality caveat (masking). Only a note on what happens with an invalid or unknown ID would make it fully self-sufficient.

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?

Schema coverage is 100%, so the baseline is 3. The description earns above baseline by translating the bare enum values into content the agent can reason about — "risk analysis", "publisher-email change history", "store ranks" — making it clear which include values answer which questions, though it does not state cost or payload size per section.

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?

States a specific verb and resource ("Retrieve details for one extension or app") and then enumerates exactly which fields come back: publisher, install count, rating, version, category. The word "one" scopes it against bulk siblings like search_extensions and compare_extensions without needing to name them.

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 single-entity framing implies this is the lookup tool rather than a search or comparison tool, but no sibling is named and no explicit when-to-use/when-not-to-use rule is given. An agent must infer from the sibling names that search_extensions and compare_extensions cover other paths.

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

All Chrome-Stats toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources