Chromium Commits Query Tool
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_chromium_latest_commitA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as retrieving the latest commit information for a specified file in the Chromium repository, making it distinct by default.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'get_chromium_latest_commit' follows a clear verb_noun pattern, which would be consistent if more tools were added, but as a standalone, it sets a good precedent.
A single tool is too few for a server named 'Chromium Commits Query Tool', which suggests a broader scope for querying commits. This minimal set limits functionality, as it only handles the latest commit for a file, lacking operations like searching commits, getting commit history, or querying by other criteria.
The tool surface is severely incomplete for the implied domain of Chromium commit queries. It only provides the latest commit for a file, missing essential operations such as retrieving commit details by hash, listing commits over time, or filtering by author or date, which are typical for commit query tools.