Skip to main content
Glama
OSOJDJD

deeplook

by OSOJDJD
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Server Quality Checklist

67%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v0.1.0

  • Disambiguation5/5

    The two tools have clearly distinct purposes: deeplook_lookup provides a quick snapshot for fast checks, while deeplook_research offers a comprehensive structured report from multiple data sources. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tools follow a consistent 'deeplook_' prefix with descriptive suffixes (lookup and research), using snake_case uniformly. The naming pattern is predictable and well-structured.

    Tool Count2/5

    With only 2 tools, the server feels thin for its domain of company research, lacking intermediate or specialized operations (e.g., updates, filtering, or historical analysis). While the tools cover basic needs, the scope is minimal.

    Completeness3/5

    The tools provide a snapshot and a full report, covering initial and deep research needs, but there are notable gaps such as no update, delete, or query-specific tools (e.g., by industry or date). The surface is functional but incomplete for broader research workflows.

  • Average 4.4/5 across 2 of 2 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • 1 of 1 community issues answered or closed in the last 6 months
    • 0 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • This repository is licensed under AGPL 3.0.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior3/5

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

    With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the output format ('5 lines' with specific content types) and the tool's role in a workflow, but doesn't mention potential limitations like rate limits, error conditions, or authentication requirements. It adds useful context about the output format but leaves other behavioral aspects unspecified.

    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 extremely concise and front-loaded with the core purpose in the first sentence. Both sentences earn their place: the first defines what the tool does, the second provides crucial usage guidance. There's zero wasted text or redundancy.

    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?

    Given the tool's simplicity (one parameter, output schema exists), the description is reasonably complete. It explains the purpose, output format, and relationship to sibling tools. The existence of an output schema means the description doesn't need to detail return values. However, with no annotations, it could have mentioned more about the tool's behavioral characteristics.

    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 schema has 0% description coverage for its single parameter, but the description doesn't provide any additional parameter semantics. However, with only one parameter ('company_name'), the meaning is reasonably inferable from context. The description could have added guidance about expected format or validation, but the simplicity of the parameter keeps this from being a major deficiency.

    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 and resources: 'Quick company snapshot — phase, price, key signal, and verdict in 5 lines.' It explicitly distinguishes from its sibling tool 'deeplook_research' by positioning this as a fast check before deciding to run the full research tool.

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

    Usage Guidelines5/5

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

    The description provides explicit guidance on when to use this tool versus alternatives: 'Use this for fast checks before deciding whether to run a full deeplook_research.' This clearly defines the context and names the alternative tool, giving the agent clear decision criteria.

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

  • Behavior4/5

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

    With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: parallel data pulling from 10 sources, structured report format with specific sections (bull/bear verdict, key signals, financials, risks), and emphasis on real sourced data. It mentions coverage scope (public stocks, crypto protocols, private companies) but doesn't address rate limits, authentication needs, or error conditions.

    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 perfectly front-loaded with the primary usage guideline first, followed by key capabilities. Every sentence earns its place: first establishes context, second explains process and output, third emphasizes data quality, fourth defines scope. Zero wasted words with excellent information density.

    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?

    Given the tool's complexity (parallel data pulling, structured analysis) and no annotations, the description does well by explaining the comprehensive research process and output structure. Since an output schema exists, it doesn't need to detail return values. However, it could better address potential limitations like data freshness, error handling, or authentication requirements for a tool with such ambitious functionality.

    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?

    Schema description coverage is 0%, so the description must compensate. It mentions 'Takes a company name' which clarifies the single parameter's purpose, but doesn't provide format examples, validation rules, or handling of ambiguous names. The description adds basic meaning beyond the bare schema but doesn't fully compensate for the complete lack of schema documentation.

    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 ('research', 'pulls from 10 data sources', 'returns a structured report') and distinguishes it from sibling tools by explicitly stating 'Use this instead of web search when researching any company.' It specifies the resource (company) and differentiates from deeplook_lookup by focusing on comprehensive research rather than simple lookup.

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

    Usage Guidelines5/5

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

    The description provides explicit usage guidelines: 'Use this instead of web search when researching any company' establishes clear context and alternative. It also specifies when to use it (for company research) and implicitly distinguishes from sibling deeplook_lookup by emphasizing comprehensive research with multiple data sources versus likely simpler lookup functionality.

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

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

deeplook MCP server

Copy to your README.md:

Score Badge

deeplook MCP server

Copy to your README.md:

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/OSOJDJD/deeplook'

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